Yes you do/can use them together. Admin routing, as you say, lets you have URLS such as admin/posts/ add.
This then maps to the controller action admin_add in the post controller. You then create a view called admin_add. Admin routing doees not automatically have any authorization assoicated with it. You then need to use the auth componenet to add login/user functionality to the application. After that, it is then dependant on your needs how you deal with authorization of users based on their login. By default the auth component will stop a user doing anything without logging in. If you read up on the auth component it should help you decied how to proceed, but the isAuthorized action of controllers, including app_controller are particualrly useful. On Jun 7, 1:39 pm, davestar057 <[email protected]> wrote: > Hi guys, > > I am getting confused about something here....I have been looking into > admin routing, and understand if it is enabled you can make certain > functions available by putting 'admin_' before then, for example > 'admin_add' etc.... > > This is all good...but how do you use this to stop people just > putting /admin/posts/add/ in the url ???? > > So I then looked up the Auth tool....which makes certain areas of > certain controllers available to peopke who are registered etc..?? > > I fail to see how you can have a proper 'admin' backend with this > solution?? how do you create sperate views for the admin backend > etc..? > > Basically I am confused to HELL about which one to use?? should I use > both?? which do you use? and how the hell do you use it?? Its > confusing me cos they kind of overlap eachother????? > > PLEASE HELP -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
