You may be trying to over-complicate it. My solution was to create a HomeController, with method admin_index, then in the routes file I added a route for admin/ that pointed to the controller home and method admin_index.
At the moment, mine is still pretty Web1.0 but I intend to use a Ajax interface that has links or tabs at the top of the view and when you click on them, it loads in each view you need to the update div area. I haven't implemented it, its still on paper but some experiments with similar stuff showed some promise. Tane On 4/12/07, RLR <[EMAIL PROTECTED]> wrote: > > I would like to create an administration area in my application where > an admin user can edit the preferences, administrate users and groups, > edit access controls and so forth. > > The settings are stored in the database and I have baked controllers > and models for each of the db tables. > > Due to the fact that there are many tables required I can see that I > will have problems providing a menu with all the controller names and > functions I need. > > Currently I do not know how to go forth at creating a unified > solution. Should I create one giant admin controller which "uses" the > models and has functions like > > users_list > users_edit > users_delete > groups_list > groups_edit > groups_delete > etc. > > > Any insight on how to accomplish this kind of task would be great. > > Thanks > Ronald > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [EMAIL PROTECTED] 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 -~----------~----~----~----~------~----~------~--~---
