Sorry, yes, I've built most of the Content model & controller, and I'm wanting to build additional model/controller extensions essentially for enhanced functionality
I don't see how I could apply $uses within ContentController, as ContentController is what i'm wanting to use but now that I'm thinking about this more, maybe I should move the generic ContentController code into a behavior On 6/22/07, Repsah <[EMAIL PROTECTED]> wrote: > > It looks to me that you are trying to build a controller... > > That business should be in your ContentController which $uses all the > models that you want, although I'm not a great fun of "generic" > controllers. > > On 6/22/07, Jonathan Langevin <[EMAIL PROTECTED]> wrote: > > > > I'm building a generic Content model, and I would like to build > > extensions such as Posts, News, etc, that would use Content for > > processing/storing the main posted content, while additional information for > > each item would be stored in it's own model ( i.e.- a forum post would > > include info like the user signature, if I wanted to keep a per-post > > signature record, etc) > > > > What would be the best way to implement this? using extend, or $actsAs, > > or $uses, etc? > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
