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 models are the same in each. Cake doesn't automatically build admin interfaces for you, so you have to build it yourself. I don't know that there's a framework out there that does that (and no, symfony doesn't count, since it only does the basics, much like cake's scaffolding and bake.php). However, you should take a look at scaffolding (and bake.php) in the cake manual. Scaffolding does your basics, but again to get anything useful you'll have to build it yourself.
On Jul 28, 9:24 pm, 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 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 -~----------~----~----~----~------~----~------~--~---
