AD7six wrote: > do you mean a CMS (that anybody can use) or you mean you (as a > developer) want to be able to manage the content?
One developer will maintain text etc. It will not be available to the public. AD7six wrote: > Storing the text in a database, would just mean something that is (in > princple) very similar to the blog tutorial. > Storing images in the database is quite easy, if you generate the links > for your images in the form <a > href='/MyImageControllerName/Display/ImageID /> then if you create an > image controller, with a function display, that reads from the db the > image with the id ImageID, outputs the correct headers and dumps the > image data - that´s that task completed. 'MyImageControllerName' can > be anything, you could call it ImgController and for any file that > isn´t in your root /img/ folder, this controller would be triggered. I have already created the controller that will handle files, but thanks anyway. http://cakebaker.wordpress.com/2006/04/15/file-upload-with-cakephp/ > Acccess control would just mean (for example) setting a session > variable when someone logs in, and checking for this session variable > to display 'admin' content. You should also put a check in the > beforeFilter of your controller (or app controller if you want acl site > wide in one call) so that should anyone guess the right url they don't > get access to something they shouldn't. you could do something like > if ($Session['MemberLoggedIn']) { > $this->renderElement("AdminActions"); } > In your view/layout to keep the views simple and the logic easily > seperable. That was exactly what I had in mind. :) AD7six wrote: > Assuming that you mean a CMS for a single site, I do. AD7six wrote: > you don´t need a text > controller, there is an inbuilt one named "pages" that is used to > display static content. It isn´t too difficult to create a controller > to edit your static pages, Do you have a link to a tutorial? I would like to see this in action.. AD7six wrote: > should that be required. A contact form > requires a form target and as such it´s best to give it it's own > controller. This is not required at the moment. Contact is just a simple page with some address information etc. (text) > If you pages are static in nature (dont require controller logic) use > the pages controller. You can use routes such that /forside is > understood by cake to mean /pages/display/home. > > I hope this helps answer some of your questions, > > Cheers, > > AD7six Thank you for your detailed answer. Best regards. Asbjørn Morell. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
