legacy-knowledge-base
公開されました Jun. 30, 2025

Using an Editor Config Contributor Client Extension in web contents

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.

legacy-article

learn-legacy-article-disclaimer-text

Issue

Apply a config contributor using a client extension to CKEditor in web content following the official documentation or the provided example does not show any changes in the web content editor.

Environment

  • Quarterly Releases

Resolution

The main issue is that the filter applied in client-extension.yml does not include the editor:

editorConfigKeys:
- description
- sampleAlloyEditor
- sampleClassicEditor
- sampleLegacyEditor

If you want to add this editor, you need to modify the client-extension.yml file by adding rich_text to editorConfigKeys or removing this configuration entirely (in that case, no filter is applied).

editorConfigKeys:
- description
- sampleAlloyEditor
- sampleClassicEditor
- sampleLegacyEditor
- contentEditor
- rich_text
- descriptionMapAsXMLEditor

Additional information

  • There is an issue that causes a duplicated button after adding a plugin. Please open a ticket to apply the hotfix LPD-21017 to resolve the issue.

     

     

     

 

did-this-article-resolve-your-issue

legacy-knowledge-base