Opt-in Controller, CMS (Pages) & controller class, a little bit confuse
Hi I'm new in fuelcms, just setup version 1.4 and start to play. Very impressive of the performance but I'm a little confuse about the controller.
If I have a controller class defined (let's say 'About'), and the only method is index, so that I can visit http://mysite/about
without problem, I created a view file in /fuel/application/views/test/demo.php (without controller class and variable file) and I can browse http://mysite/test/demo
, it is opt-in controller, so far so good. But when I created a view file at /fuel/application/views/about/contact.php, it return 404. Is it because I'd a controller class "About", so that all view files in folder '/fuel/application/views/about/' not work (even I didn't have the filename same as any method name in the controller class)
After that I create a page in admin CMS which I set the location to 'about/team (no view file and variable file, just put some content in body variable). And same as before, when I go http://mysite/about/team
, it return 404 too (I checked the /fuel/application/config/MY_fuel.php, fuel_mode is set to AUTO)...
So my question is : is it - once the controller class exists (even though the class didn't have a match method name to uri method segment), both admin CMS page and opt-in controller not work ? Or should I need to set something in config file ?
Thanks a lot !