I know about CAKE_ADMIN parameter but I don't think that's the best way to control the content. I have to create separate layout, separate listing with pagination, separate search facilities. Basically every task has to be done twice.
I was hoping that someone may be able to point out a very big con of including admin tasks into the content page. :) On Jun 29, 4:30 pm, francky06l <[EMAIL PROTECTED]> wrote: > check the CAKE_ADMIN parameters, and the 'admin' routing. I suppose > it's exactly what you describe. > > On Jun 29, 5:19 pm, "[EMAIL PROTECTED]" > > <[EMAIL PROTECTED]> wrote: > > Hi, > > > In the past I used to create separate admin section on the website to > > control the content (users, articles, images, etc.). And I was > > thinking it may be easier and BETTER to create additional links for > > admin tasks in the actual pages (front-end). Let's say if we have a > > page with article and the user is logged in as an admin he/she would > > see additional links: > > *edit this article > > *delete this article etc. > > > Just like it is done in Drupal CMS. > > > I know it may differ from project to project but what if we would talk > > about "standard" website with categories+articles. > > > Which approach do you prefer? --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
