Suggestion - for a simple approach, you might try the following: use admin routing, and in your appController check for "admin_" prefix in the action part of the url. If it is there, do the auth checks.
Your controllers don't need to be involved in auth checking for admin if you follow this approach. If you want more complex authorization you might need something more involved. But for most simple admin sections, this is pretty functional. On Jul 29, 6:24 am, Pento <[EMAIL PROTECTED]> wrote: > Thanks, but I think that it's very poor admin interface and all my > contollers will be mixed with checks of privileges. > And in point of fact Admin Interface is simply different application > but with same models > > On 23 июл, 18:27, cauld <[EMAIL PROTECTED]> wrote: > > > Have a look at the advanced routing configuration in section 4 in the > > manual (http://manual.cakephp.org/chapter/configuration). This should > > give you what you need. > > > On Jul 22, 10:49 pm, Pento <[EMAIL PROTECTED]> wrote: > > > > So, there are usual site andadminarea for add some news, materials > > > and so on. > > > It's good idea to make thisadminarea on subdomain (for example, > > >admin.somesite.org)? > > > As I think it's only one way for it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
