Check out this thread:
admin backend best practice
http://groups.google.com/group/cake-php/browse_frm/thread/7e14ca05b59e27f/d8e76d231cc58d15?lnk=gst&q=admin+best+practice&rnum=3#d8e76d231cc58d15
--~--~-~--~~~---~--~~
You received this message because you are s
Well, that's a matter of opinion, but the other way you can do this is
by putting your cake core into a root folder, and then referencing
your cake app folder config files to that cake core location, so you
can have a separation of production and admin interfaces. You'd just
have to make sure your
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 appro
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 routin
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 and admin area for add some news, materials
> and s
how about using CAKE_ADMIN ?
On Jul 23, 1:49 am, Pento <[EMAIL PROTECTED]> wrote:
> So, there are usual site and admin area for add some news, materials
> and so on.
> It's good idea to make this admin area on subdomain (for example,
> admin.somesite.org)?
> As I think it's only one way for it.
So, there are usual site and admin area for add some news, materials
and so on.
It's good idea to make this admin area on subdomain (for example,
admin.somesite.org)?
As I think it's only one way for it.
--~--~-~--~~~---~--~~
You received this message because you
