Custom Widget for Advance link Builder Experience in AEM RTE Content Fragment Editor not working with getwidget / getcustombutton extensions using React adobe app | Community
Skip to main content
T
tiru35
Level 2
June 4, 2026
Question

Custom Widget for Advance link Builder Experience in AEM RTE Content Fragment Editor not working with getwidget / getcustombutton extensions using React adobe app

  • June 4, 2026
  • 1 reply
  • 27 views

I am trying to build a custom widget for external links in a new content fragment editor RTE and store those values into an anchor tag. I have tried both the options to use getwidget and getcustombutton options, but looks like the getcustombutton options is deprecated. I am able to run the build with my custom code using getwidget function and don’t see any errors in the console logs. Also, I don’t see an option to view the pop-up using the curly brace option. Can someone help me with the limitations with extensibility options?

1 reply

G
Adobe Employee
goelsAdobe Employee
Adobe Employee
June 5, 2026

Hi ​@tiru35 

 

Yes— what you're seeing is consistent with the current limitations / transition state of the new Content Fragment Editor RTE.

Two important points:

  1. RTE widgets are not opened from a toolbar "curly brace" icon.
    The widget flow is: click into the RTE field, type {, then select your widget from the context menu. Add widgets to Rich Text Editor (RTE) Extensible Services Test Cases

  2. The old RTE extension APIs are in flux / deprecated for newer RTE implementations.
    Adobe introduced CF Editor RTE extensibility with toolbar buttons, widgets, and badges, and the older RTE extension endpoints as deprecated. AEM Content Fragments extensions Release Notes for 2026.3.0 release of Adobe Experience Manager as a Cloud Service.

T
tiru35Author
Level 2
June 5, 2026

Thanks for responding. I have not used the toolbar for option 1. I am using the RTE field to enter the curly braces to open the context menu but nothing happens as my AEM content fragment editor is not calling the widget extension after it’s successfully registered and my extension loaded.

Terms & ConditionsAccessibility statement

Loading footer...