Multifield plugin for the new CF Editor

[daniel-strmecki]

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

[TarunKumar]

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

[daniel-strmecki]

Hi @TarunKumar,

thanks for the info, but the problem is we are not starting from scratch here. We already have a large number of content fragments created in the old editor using a custom multifield storing data as subnodes.

Therefore, I need to evaluate whether we can build a similar multifield plugin for the New CF Editor or switch to using CF references as you suggested. However, our editors do not prefer the second option, as it requires changes in WoW and content re-building with scripts.

Daniel

[PRATHYUSHA_VP · Accepted solution]

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-work...

Thanks

[daniel-strmecki]

Hi @PRATHYUSHA_VP,

thanks, looks like we will go the same path. It is a little bit disappointing for editors that we cannot define a multifield with multiple input fields, but I guess they need to learn to live with it.

[kautuk_sahni]

@daniel-strmecki Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!