I like to do all the client system first, then I do another system, completly diferent to admin stuff. Even cake having the admin route, I dont like to use it. That way, I can put it in another url, so, guessing my admins urls is not a trivial thing... so, if one day, someone find a bug in cake admin route, my systems will be safe.
I just heard that there is some robots scanning cake's urls for an open scafold. So, I just want to prevent this things. I dont know if it is the better way, but the work is the same. sry my bad english. -- Renato de Freitas Freire [email protected] On Tue, May 18, 2010 at 5:38 AM, Andrei Mita <[email protected]> wrote: > Hello, > > I'm getting ready to start a real project using Cake and the first question > is: how to separate controllers, actions and views for end-users and admins. > > I mean, is there a recommended way of doing the splitting or is it enough > to create separate actions for end-users and for admins? > > For instance is it OK to have in Articles controller index() and > admin_index() ? > > Thanks > > Check out the new CakePHP Questions site http://cakeqs.org and help others > with their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<cake-php%[email protected]>For > more options, visit this group at > http://groups.google.com/group/cake-php?hl=en > Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" 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
