I am currently customizing the Rich Text Editor (RTE) using App Builder.
I am implementing it according to the documentation, but even after inputting the ID for the h1, it is not being removed from the tool.
rte: {
removeButtons: () => [
{
id: "h1",// not work
},
{
id: "bold", //work
}
],
}
Could the ID be incorrect? I would appreciate it if you could share any information you might have.
Views
Replies
Total Likes
Thank you for your reply, and I apologize for my delayed response.
I also reviewed the documentation and tried to implement it, but unfortunately, I couldn't get it to work. For now, this development has been put on hold, but I would greatly appreciate it if you could share any additional information you come across. Thank you for your continued support!
Views
Replies
Total Likes
@太郎榊原1 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Hi @太郎榊原1 ,
Correct Way to Remove Heading Options in RTE:
The headings (H1–H6) are typically provided through the format plugin, and not as individual buttons like "h1", "h2", etc.
To remove heading options, you need to:
Target the format plugin
Remove the undesired options from its config
Working Code Example
rte: {
plugins: {
format: {
features: ["p", "h2", "h3"], // only keep desired options here
},
},
removeButtons: () => [
{
id: "bold", // works as expected
},
// Don't include 'h1' here — it's not a button by ID
],
}
Key: "h1" is not a button that can be removed via removeButtons. It’s part of the "format" plugin and must be excluded through its config.
If Using removePlugins
You could also remove the entire format plugin like this:
rte: {
removePlugins: () => ["format"], // removes entire heading dropdown
}
But usually, it's better to keep format and just limit its options (as shown above).
This behavior aligns with the official Adobe Experience Manager RTE plugin system, where heading styles are managed via format/formatselect.
Regards,
Amit
Thank you for your response.
I implemented the changes you suggested, but I was unable to remove either the entire formatselect menu or individual tools such as certain heading options.
Our AEM as a Cloud Service environment is on the latest version thanks to automatic updates.
We are currently using “@adobe/uix-guest” ^0.8.0, and upgrading it to 1.0.0 did not make any difference.
If you have any additional information, I would greatly appreciate it.
Views
Replies
Total Likes
@太郎榊原1 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!
Views
Replies
Total Likes
This problem still hasn’t been solved yet
Views
Replies
Total Likes
Views
Likes
Replies