Thanks for your reply! I agree with everything that you say. To me, it's kinda non conventional to mix the admin_* methods within non .. mostly because you can't look at the controllers and discern which ones have those methods until you open up the file. This way through a plugin you know what each controllers specifically does. Also, with plugins having their own AppController, you can easily set menus, etc ..
Also, this is a breeze for ACL because you can wildcard controllers with Admin*:* (using felix g's SimpleAcl) On May 18, 11:27 am, Greg <[EMAIL PROTECTED]> wrote: > It also depends on how many people are working on your application. > If, say, you have an admin programmer who only works on the admin > section of your app, and a public side programmer who sticks to the > non-admin areas, the project would be rather difficult to manage if > you > were to go about the admin_* route. You would constantly have more > than one person modifying a file at a time, which becomes a complete > hassle when using svn or some other versioning system. > > So, as far as I know, your other options are to go with a plugin, or a > completely separate app. I am not sure about the overhead with > plugins, > I am really new to Cake still, so I need to do some more research on > that. > I am about to jump into the same situation you are, and I would like > to > use plugins, it just seems more logical from first look. > > ...and there's my 2 cents. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
