ナレッジベース
公開されました Jun. 30, 2025

CKEditor Customizations Not Applying to Translations or Forms

written-by

Daniel Martinez Cisneros

knowledge-article-header-disclaimer-how-to

knowledge-article-header-disclaimer

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

ナレッジベース