[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24429#action_24429
 ] 

Hudson CI server commented on MAGNOLIA-2811:
--------------------------------------------

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-4.1-branch 
#2|http://hudson.magnolia-cms.com/job/magnolia_main-4.1-branch/2/]
     backport of r28283 and 28284 from 4.2 into 4.1.2. 


> contentNodeName parameter of editBar puts the paragraph node into the same 
> tree level as the page is, not as a child of the page
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2811
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2811
>             Project: Magnolia
>          Issue Type: Bug
>          Components: taglibs
>    Affects Versions: 4.1
>            Reporter: Zdenek Skodik
>            Assignee: Zdenek Skodik
>             Fix For: 4.1.2, 4.2
>
>
> there is a existing workaround to protect from this bug:
> *  move the content node to appropriate website tree by your own using JCR 
> Browser -
> new paragraphs are added correctly and the content is displayed as expected.
> * don't use the contentNodeName attribute of the editBar tag which exctract
> the related node data of the paragraph under the appropriate website tree and 
> then
> leave it as it is or create the content node by your own and move your node 
> data under it.

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

        

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to