-
Bug
-
Resolution: Fixed
-
Major
-
4.1
-
None
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.
Acceptance criteria
- is cloned by
-
MAGNOLIA-2885 editBar: if a non-existing singleton paragraph is edited, the newly created paragraph will be placed as a sibling of the page
- Closed
- is related to
-
MAGNOLIA-2741 Different behavior of uuidLink Control in STK and 'classic' templating
- Closed