I've used this before and it works well, with the ability to cache the element easily as well.
http://bakery.cakephp.org/articles/view/creating-reusable-elements-with-requestaction However, many people advise against using (abusing?) requestAction as it executes a whole new page request. If you cache the output however, it can be a good technique. Cheers, Adam On Oct 1, 9:59 am, Jimmy Bourassa <[EMAIL PROTECTED]> wrote: > I've been thinking about how to do this cakelike and so far I haven't > found anything that is not messy (and mostly because I am fairly new > to cake should I say) > > Heres what I would like to do. I have Games and Events. On my > homepage, I want a "Coming up" section to show, let's say, the next > five event/games ordered by date. > > So basically I need to gather information from two different models in > one single view (or element I think it'll be). And I need to be able > to order the whole lot by date. > > Should I create a controller that uses ($var uses) Games and Events? > > Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
