Custom editor configuration is not applied to repeatable fields
Written By
Alfonso Crisci
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- After implementing a custom
EditorConfigContributor to override the configuration of a web content editor, e.g. as below:
@Component(
immediate = true,
property = {
"editor.name=alloyeditor",
"javax.portlet.name=com_liferay_journal_web_portlet_JournalPortlet",
"service.ranking:Integer=100"
},
service = EditorConfigContributor.class
)
developers may notice that the configuration in a structured web content with repeatable HTML fields is only applied to the ancestor of the fields and not to the repeated ones.
Resolution
- To target the repeated web content fields, add the
com_liferay_dynamic_data_mapping_web_portlet_DDMPortlet name as well:
@Component(
immediate = true,
property = {
"editor.name=alloyeditor",
"javax.portlet.name=com_liferay_journal_web_portlet_JournalPortlet",
"javax.portlet.name=com_liferay_dynamic_data_mapping_web_portlet_DDMPortlet",
"service.ranking:Integer=100"
},
service = EditorConfigContributor.class
)
A sample module is hereby attached
Did this article resolve your issue ?