I've been using CakePHP for almost 2 years now, and I still don't know what the best way to do this is. The way I do it is I end up creating an added action in one of my controllers, and I change the routing for the homepage to point there. I'd really like to know of a better approach to this, as I haven't found any good real-world example.
On May 20, 2:17 pm, W Marsh <[EMAIL PROTECTED]> wrote: > Hi. > > If you look at most web sites you will see that their index pages are > generally a mish-mash of different functionality. For example, they > might give a summary of recent blog posts coupled with other > statistics, all relating from various models in the system. > > How does this fit into the model-view-controller mentality? > Controllers and models tend to be focused on one specific piece of > functionality in the examples I've seen. There are no good examples of > real world usage. > > I should point out this is a design/best practices question. I know > HOW to make an index/general purpose page work, but I would like to > hear some wisdom on how to do it in the CakePHP spirit. > > Thanks. > > - Wayne --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
