Incorrect XPM Component field markup when 2+ levels of multivalue embedded fields #105
Comments
|
I suspect the logic in FieldPath is incorrect somewhere around here: https://github.com/sdl/dxa-web-application-java/blob/58a4fdebafc192b9a87570c684bd97d9091fdc5f/dxa-framework/dxa-common/src/main/java/com/sdl/webapp/common/api/mapping/semantic/config/FieldPath.java#L63 |
dxa-team
pushed a commit
that referenced
this issue
May 24, 2018
…3183 to develop * commit 'f467f43bee00823cb3b58f6d2ea007684c3b9ed4': Added UGC Module to pom's
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you have a content model which uses 2 levels of multivalue embedded fields (for example schema Article contains multival embedded field Paragraph, which contains multivalue embedded field Link) then the XPM markup generated for the fields within the lowest level is incorrect:
<!-- Start Component Field: {"XPath":"tcm:Content/custom:Article/custom:paragraph[2]/custom:link[1]/custom:link/custom:linkText[1]"} -->instead of
<!-- Start Component Field: {"XPath":"tcm:Content/custom:Article/custom:paragraph[2]/custom:link[1]/custom:linkText[1]"} -->The text was updated successfully, but these errors were encountered: