Knowledge Base
Published Jun. 30, 2025

CKEditor Customizations Not Applying to Translations or Forms

Written By

Daniel Martinez Cisneros

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.

Issue

  • Customizations made to CKEditor using an `EditorConfigContributor` are only applying to the editor when editing Web Content, but not in the editor for translations (accessed through Control Panel > Content Actions > Translate) or in paragraph fields within Forms.

Environment

  • Liferay DXP 7.4
  • Liferay 2025.Q1+

Resolution

The CKEditor customizations must target the correct portlets to be effective. By default, the Web Content portlet is targeted. To apply the same customizations to other portlets such as Forms and Translations, configure the `EditorConfigContributor` to target them as well.

Add the javax.portlet.name property to the @Component annotation, specifying the portlet names where the CKEditor customizations should apply. For example:

@Component(
immediate = true,
property = {
"editor.name=ckeditor",
"editor.name=ckeditor_classic",
"javax.portlet.name=com_liferay_dynamic_data_mapping_form_web_portlet_DDMFormAdminPortlet",
"javax.portlet.name=com_liferay_translation_web_internal_portlet_TranslationPortlet",
"javax.portlet.name=com_liferay_journal_web_portlet_JournalPortlet",
"javax.portlet.name=com_liferay_dynamic_data_mapping_web_portlet_DDMPortlet"
},
service = EditorConfigContributor.class
)

This configuration ensures that the defined customizations are applied to the CKEditor instances used by the Web Content, Forms, and Translations portlets.

Additional Information

 

Did this article resolve your issue ?

Knowledge Base