I think I just got an answer for my own question. Looking at the pages
controller, all you really need to do is make a new controller, set
its $uses property to an emtpy array, and then in its action use $this-
>render('whatviewtouse.ctp');On Sep 10, 2:27 am, Kenchu <[EMAIL PROTECTED]> wrote: > Not all my pages (views) can be linked to a specific model/controller. > For example. Imagine a welcome-page of a game-site. On it you'll see > alot of different things, not only connected to a single table. It > might show some news, some popular forum posts, as well as a list of > logged in users. Now where would all the logic for this page be done? > In the users controller? In the forum-post controller? In the news > controller? None is really more fitting than any other. Sure I > supposed you COULD just decide to do everything in, lets say, the news > controller in the action 'home', where you submit custom queries to > the database, but that doesn't seem like a good solution. It doesn't > look nice from a system modelling point of view. > > So how would you tackle this problem? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
