It probably wouldn't be a good idea to buck the convention of putting controllers in the Controllers folder.
However, if you feel you can split controllers out into modules, perhaps using plugins to group logical sets of MVC code. Or, consider merging some controllers together, especially if the functionality can be grouped into modules, and there are no action clashes. Out of interest, how many controllers do you have? In one project I have, there are 36 controllers and 50 models, and there's still a bunch of legacy code to convert to CakePHP. I've not yet felt the need to organize into plugins yet. In fact, it's nice to be able to see all the controllers in one directory, instead of scrambling through multiple directories. Regards Reuben Helms On Tuesday, 10 June 2014 23:13:48 UTC+10, Lucian Vasile wrote: > > Hello! > > I was wondering if controllers can be grouped in folders in order to have > a cleaner Controllers folder and maybe to have them separately grouped into > modules. > > Thanks! > -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/d/optout.
