[ 
http://jira.magnolia.info/browse/MAGNOLIA-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Haderka closed MAGNOLIA-2174.
---------------------------------

    Resolution: Cannot Reproduce
      Assignee: Jan Haderka  (was: Fabrizio Giustina)

Failed to reproduce on 3.6.1. Either it have been fixed in between, or there is 
some issue with your templates.
If you can provide paragraphs & templates necessary to reproduce the issue 
attach them and reopen.

> Nested Paragraphs don't work properly
> -------------------------------------
>
>                 Key: MAGNOLIA-2174
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2174
>             Project: Magnolia
>          Issue Type: Bug
>          Components: taglibs
>    Affects Versions: 3.5.4
>         Environment: Mac OSX, FireFox, Mg 3.5.4, Tomcat 5.5
>            Reporter: Giancarlo Berner
>            Assignee: Jan Haderka
>            Priority: Blocker
>
> We are encountering a strange behavior with nested paragraphs.
> What has been done:
> - We created a "Front Panel" paragraph with a content node collection name
> - Within that paragraph script there are 3 "DIV-styled" columns.
> - Each column has a "contentNodeIterator" tag with each having it's own 
> content node collection name.
> - Each column has a "New bar" tag with the matching content node collection 
> name.
> - The new bar allows the author to select one of the available paragraphs.
> We are noticing that the content node iterator of the first column never gets 
> executed. Only the New bar is visible. We can add as many new paragraphs as 
> we want they are never visible. However, the other two columns work fine. The 
> contentNodeIterator of column 2 and 3 work as expected, displaying each sub 
> paragraph with the edit bar and at the end the new bar.
> We also noticed in the JCR Browser that the "Front Panel" paragraph and the 3 
> column paragraphs are all on the same level as child of the current page.
> We set the status to "Blocker", because this error is holding as back from 
> going into the testing phase. One workaround is to not use the 
> cms:contentNodeIterator tag, but we nevertheless would like to fix this issue.
> Thanks a lot!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to