Content Fragment New Editor - Disable Richtext button

[30991930w169]

Hi,
In my project we need to exclude some features present in the richtext toolbar.(example: remove the button for uploading images)
I have read some of the official documentation, but it is not clear to me how to do .
Also how can I test any fix in the local environment? the new interface seems not to be accessible from there.
I hope you can help me,
Thank you

[AmitVishwakarma]

Hi @30991930w169 ,

Customize the RTE via rtePlugins Configuration:

Step 1: Understand Where It Applies

In AEMaaCS, Content Fragments are authored using Structured Content Models. Each text field (of type multiline) can be configured with RTE plugin settings.

Step 2: Configure rtePlugins in the Content Fragment Model

  - Go to: Tools → Assets → Content Fragment Models

  - Select your model → Click Edit

  - For the field using Rich Text:

    - Select the field (type: Multiline Text)

    - On the right panel, change the "Multiline Text Type" to "Rich Text"

    - Scroll down to "Editor Configuration"

    - Click "Configure"

You’ll now see Rich Text Plugins (rtePlugins) like:

{
  "features": "*",
  "rtePlugins": {
    "format": {
      "features": "bold,italic,underline"
    },
    "justify": {
      "features": "justifyleft,justifycenter,justifyright"
    },
    "links": {
      "features": "modifylink,unlink"
    },
    "misctools": {
      "features": "-"
    },
    "image": {
      "features": "-"
    }
  }
}

To disable image upload:

Set the "image" plugin to an empty feature list or disable it:

"image": {
  "features": "-"
}

Example Full Editor Config (Safe, Minimal):

{
  "features": "*",
  "rtePlugins": {
    "format": {
      "features": "bold,italic"
    },
    "justify": {
      "features": "-"
    },
    "links": {
      "features": "modifylink,unlink"
    },
    "image": {
      "features": "-"
    },
    "misctools": {
      "features": "-"
    },
    "table": {
      "features": "-"
    }
  }
}
​

This disables image upload, tables, alignment, and more. Add/remove as needed.

Step 3: Test It Locally or in Dev

AEMaaCS local dev limitations:
  - The New Content Fragment Editor UI does not run properly in local SDK (http://localhost:4502) due to UI feature flags and SPA routing.
  - Best practice: Deploy your code to a DEV environment via Cloud Manager for UI testing.
  - Alternatively, test content fragment model JSON via:

/conf/<your-site>/settings/dam/cfm/models/<model-name>/jcr:content
​

(Advanced Control via Policies):

You can centrally define RTE configs using editor policies under:

/conf/<your-site>/settings/wcm/policies

 But for Content Fragments, the per-field config inside the model is the safest and most flexible.

Regards,
Amit

[30991930w169]

Hi Amit, 

thank for your reply!

I tried to implement what you told me but the "Configure" button is not present in the Content Fragment Model section.

[daniel-strmecki]

In case this is supported, I am not aware of it. I raised a feature request already some time ago: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-ideas/define-which-rte-plu...