With all the versions out there now, its no longer enough to just say 'Magnolia'. Everyone should indicate the version right up front, else, they will asked what it is.
I know you can nest collections because I did it in Magnolia 1. I had a 'home.jsp' that imported the 'header.jsp', 'left.jsp', 'footer.jsp', and 'main.jsp'. 'main.jsp' was just a table with an 'editBar', and a 'newBar'. The 'paragraphs' available via the newBar where for a single column main section, or a double column main section. These 'paragraphs' were intended to be use once per page, rather than stacking them in a column. So after adding a new page, I would need to choose what type of main section. Once I chose that, the main section would get another set of bars for stacking the content paragraphs. If I chose 'single', there would be one long set. If I chose 'double', there would be two sets, side-by-side. So you see, paragraph content in a single column page was nested in a 'single' collection, and paragraph content in a double column page (two separate collections) was nested in a 'double' collection. I had to use different "contentNodeCollectionName's". main = contentParagraph0, single = contentParagraph10, double = contentParagraph11 and contentParagraph12. This is different from the Magnolia sample site which I thought used too many JSP's. I was trying to strip it down to just what I needed for the layout my company wanted. Later I began to think the architects of Magnolia do it that way because it allows for more flexibility and greater reuse of the template JSP's. When I migrated to Magnolia 2, I still didn't emulate the sample site, but dropped the nested collection because I thought it was unneccessarily complex, and why not just have two templates, one for a single column, and one for a double. Also there was very little content in the 'contentParagraph0' collection so I thought that was a waste of space. The problem there is if I change the width of the left column, I need to change it in both templates. So I loose the ability to make a global change to the site. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 05, 2005 3:34 PM To: [email protected] Subject: [magnolia-user] Subparagraphs (or variable contentNodeCollectionName) Hi everybody!!! I'm trying to make a paragraph template which contains another contentNodeCollection inside it. So I have a page template which has the "main" contentNodeCollection (The paragraphs of the page), and in addition, in every paragraph I want another contentNodeCollection (of a different paragraph definition I have done). So I need a variable contentNodeCollectionName to can difference the contentNodecollections of every paragraph. The problem is that I can't do that. I've tried to use the first paragraph title as name: <cms:newBar contentNodeCollectionName="<cms:out nodeDataName="title">" paragraph="adieArticulo"/> But it doesn't work Have someone of you done something similar?????? Is there any possible solution?????? THANKS FOR READING ME!!!!!!!!!!! P.D: If you can send me an example... it would be a great thing ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
