Ok, I will give it a try with understanding what you are trying to accomplish!
Correct me if my understand is wrong, but: 1) You have a standard CakePHP installation with the CakePHP directory and an application "app" directory, correct? 2) You wish to use the application to provide content management of the content in the application, correct? 3) You wish that each user of your application will have access only to his/her own content in the application, correct? With that I understand that you would like something like: App --- Controller ------ a contents controller --- Models ------ a content model ------ a user model --- Views ------ Contents --------- Content views ------ etc. Thus when a user has logged in, and has chosen the CMS (contents), the contents controller gives him/her access to manage the content - modelled by the content model. Awaiting some comments from you, enjoy, John On Mar 27, 9:02 am, programguru <ja...@w3developing.com> wrote: > Hello, > > I've been hacking at this for several days, and have modified and toyed with > about 7 different tutorials with Auth, only to find none of them provide the > actual answer I am looking for - or maybe I don't know what the correct > answer is. > > Anyhow. > > All I have been trying to do is create: > > 1) A view that is user/pass protected which allows control of content for the > site. I was able to get several login systems working with Auth, but not able > to edit any content because the permissions are outside of the login scope or > something of that nature. > > I am certainly missing a link somewhere in all of this. > > 2) All controllers should be accessible from this view so the content can be > modified. > > I cannot figure out how (although I have done this a million times with > straight php/mysql) how to make this work with CakePHP. > > The problem I keep running into is the /users dir only allows access to that > dir, but I cannot create a sub directory in there for example called: CMS, > because then the controller classes cannot be accessed by the default core. > > Anyhow, Id be glad to hear any insight in how to get a stupid simple CMS page > setup with access to all of the sites editable content. > > I don't need anyone to explain how to build a db, a controller, a model, or > Bake... That's not what I am asking. > > Just a bit lost and need some direction. > > Thanks. > -- > View this message in > context:http://n2.nabble.com/simple-cms-w--auth-%3A%3A-username---password-on... > Sent from the CakePHP mailing list archive at Nabble.com. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
