The multiple-parts strategy is probably the easiest way to do it. I'm about to start on a custom Radiant-based project and I have some ideas brewing about this problem. Of course, the page/content template idea in the page-attributes fork/tweak is a wonderful strategy, if you can get it to work. I'm sure the author (Jacob?) would be willing to help answer questions about it.
Sean On 9/8/07, Andrea Franz <[EMAIL PROTECTED]> wrote: > On 9/8/07, Jeroen Janssen <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I was wondering if anyone knows if there is a page_attributes > > extension for radiant? > > (the one on the wiki is a "a Branch of Radiant Facets PLUS an Extension") > > > > Example, > > > > I have band members who play an instrument (bass, drum, piano,etc) I > > would like to have the title of a page be the name of the musician and > > an attribute with the instrument so I can easily display a short list > > of everyone on the parent page without duplicating too much > > information (this also makes it easier when someone leaves/joins the > > band). > > You could create a band page that loop through its children displaying > the title of the page > and the page part named "instrument". I think it should be easier. > _______________________________________________ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
