[MAGNOLIA-2811] contentNodeName parameter of editBar puts the paragraph node into the same tree level as the page is, not as a child of the page Created: 13/Jul/09  Updated: 23/Jan/13  Resolved: 12/Oct/09

Status: Closed
Project: Magnolia
Component/s: taglibs
Affects Version/s: 4.1
Fix Version/s: 4.1.2, 4.2

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Zdenek Skodik
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MAGNOLIA-2885 editBar: if a non-existing singleton ... Closed
relation
is related to MAGNOLIA-2741 Different behavior of uuidLink Contro... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

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.

Generated at Mon Feb 12 03:40:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.