Hi All,
In 6.1, we customized multifield nodes to be saved as a particular name like slides-1, slides-2 etc. using following xml snippet.
<slides
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/multifield"
class="list-option-carouselType-showhide-target full-width"
eaem-nested=""
fieldLabel=“Slides”
showhidetargetvalue="[basic,large]">
<field
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/fieldset"
name="./slides-$">
However for 6.4 to have rich text work with multifield, I needed to use coral multifield resource type and following xml snippet.
<slides
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/coral/foundation/form/multifield"
composite="{Boolean}true"
class="list-option-carouselType-showhide-target full-width"
eaem-nested=""
fieldLabel="Slides"
showhidetargetvalue="[basic,large]">
<field
jcr:primaryType="nt:unstructured"
sling:resourceType="granite/ui/components/foundation/form/fieldset"
name="./slides">
Here multifield nodes are saved as item0, item1 etc. under jcr:content/slides.
Can anyone let me know with 6.4 coral multifield, how can we have custom multifield names like slides-1, slides-2, etc. instead of item0, item1, etc.
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
I don't think that is feasible with OOB multifield code
Views
Replies
Total Likes
I don't think that is feasible with OOB multifield code
Views
Replies
Total Likes
Gaurav is correct - OOTB - the coral MF works like node, node1 etc. See
Building Experience Manager Components using Granite/Coral Resource Types
Views
Replies
Total Likes