I would probably add another model, Post, like you've mentioned. I would also probably create a behaviour that would exist in all the sub-post models, which would add and remove a link from the Post model on save/delete.
Although I haven't used it myself, it looks like you could then use AD7six's Polymorphic Behavior on the Post model. http://bakery.cakephp.org/articles/view/polymorphic-behavior Cheers, Adam savant wrote: > I am trying to figure out how to best display a myriad of different > posting types within the same base index page. > > To give an idea of what I am dealing with, consider a system with News > Posts and Photo Posts. Each News Post has its own MVC, separate from > the MVC for the Photo Post (different database table, different files, > different functioning, etc.). Each of these does pagination by itself > (default) and calls related items. I would like to have a main index > page that shows all of these, sorted by a datetime field in the > database which each item has. > > Each one is different enough such that I wouldnt have a relationship > between them other than calling them all "Posts", which I can if it > renders a solution. I don't know quite how to show different data > within the same page as if it were functionally the same. Is there > something simple that I am missing, perhaps a helper, out there? It's > most likely best to envision the app as a blog-like application > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
