Multifield plugin for the new CF Editor

Question

Hello,on my project, we have a custom multifield enabled for Content Fragments. Now I want to evaluate if we can continue to use this approach when we migrate to the new Content Fragment Editor.I was curious if someone already tried to build a plugin/extension like that? I see there are many example extensions in the docs, but they are not so complex as defining multiple custom fields that get stored as subnodes.Worst case, I will try to do it from scratch, but I was curious if other projects have the same problem and if someone already tried it so we can exchange know-how. Thanks,Daniel

PRATHYUSHA_VP · Accepted Answer

Hi @daniel-strmecki

We did face similar issue when we switched to new content fragment editor -

After discussion on the similar topic, we decided to go with fragment reference rather than using the custom multifield because we faced additional issues on the same -

You can find that topic below -

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/nested-multifield-not-working-after-upgarding-to-aem-6-5-15/td-p/611550

Thanks

TarunKumar · Answer

Hi @daniel-strmecki ,

You can define a CF model then this model effectively defines the structure of the resulting content fragments using a selection of Data type. Using the model editor you can add instances of the data types, then configure them to create the required fields.
One of the data type is Fragment Reference which can be used to

References other content fragments;
The data type can be configured to allow fragment authors to:
- Edit the referenced fragment directly.
- Create a new content fragment, based on the appropriate model

Note: The multiple composite multifields feature is currently in beta.
Link: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/content-frag...

-Tarun

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded