Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

Configure the Rich Text Editor plug-ins | AEM Community Discussion

Avatar

Administrator

BlogImage.jpg

Configure the Rich Text Editor plug-ins by Adobe Docs

Abstract

RTE functionalities are made available via a series of plug-ins, each with features property. You can configure the features property to enable or disable, one or more RTE features. This article describes how to specifically configure the RTE plug-ins.

For details about the other RTE configurations, see Configure Rich Text Editor.

Activate a plug-in and configure the features property
To activate a plug-in, follow these steps. Some steps are needed only when you configure a plug-in for the first time, as the corresponding nodes do not exist.

By default, format, link, list, justify, and control plugins and all their features are enabled in RTE.

NOTE
The respective rtePlugins node is referred to as  to avoid duplication in this article.

Understand the findreplace plug-in
The findreplace plug-in does not need any configuration. It works out of the box.

When using the replace functionality, the replace string to be replaced should be entered at the same time as find string. However you can still click find to search for the string before replacing it. If the replace string is entered after clicking find, the search is reset to the beginning of the text.

The find and replace dialog becomes transparent when find is clicked and becomes opaque when replace is clicked. This allows the author to review the text that the author will replace. If users click replace all, the dialog closes and displays the number of replacements made.

Read Full Blog

Configure the Rich Text Editor plug-ins

Q&A

Please use this thread to ask the related questions.



Kautuk Sahni
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

0 Replies