-
Type:
Suggestion
-
Resolution: Duplicate
-
Component/s: Macros - Core Platform
-
None
User Problem
When a user converts a page from the TinyMCE editor to the Fabric editor in Confluence Cloud, certain unsupported bodied macros are displayed as "Error loading extension." This also occurs if a macro has been uninstalled from the instance.
- In the Fabric editor, unsupported or uninstalled bodied macros are shown as "Error loading extension," and the macro content is not visible.

- In contrast, the TinyMCE editor handled this scenario by displaying an "Unknown macro" frame, while still rendering the bodied content inside the editor. This allowed users to access and recover the content within unsupported macros.

Suggested Solutions
Improve the handling of unsupported or uninstalled bodied macros in the Fabric editor by displaying an "Unknown macro" frame (similar to TinyMCE), so that users can still view and recover the macro's bodied content.
Workaround
The user could use REST API to query the macro content:
https://<site url>/wiki/rest/api/content/<contentId>?expand=body.atlas_doc_format
- duplicates
-
CONFCLOUD-83425 Add ability for unknown bodied macros to display its body contents so customer could still access it
- Closed