-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
Low
-
Component/s: Page - Editor - Migration or Conversion to Fabric
-
None
-
1
-
Major
Issue Summary
Some macros are unsupported in the new editor. After converting a page from the legacy editor to the new fabric editor, if a supported macro is wrapped in an unsupported macro the content is uneditable and shows confluenceADFMigrationUnsupportedContentInternalExtension.
Steps to Reproduce
- Create a page with a Section macro and Column macro with additional content in the Column macro.
- Save and convert the page.
- When you edit the page you'll find the Column macro wrapped in a macro confluenceADFMigrationUnsupportedContentInternalExtension.
- The supported content will not be editable.
Source: https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/
| Legacy editor elements | Category | In legacy editor | In new editor | What happens when converted? |
|---|---|---|---|---|
| Column macro | Presentation | Action exists in toolbar |
Converts completely The macro and its settings are carried over to the new editor. The settings can't be changed in the new editor. The content in the body of the macro can be edited. New layouts can be created in the new editor using the Layouts tool in the toolbar. |
|
| Section macro | Macro | |
Converts completely (reference CONFCLOUD-68508) Even though this macro was removed from the new editor, the macro and its settings are carried over to the new editor. The settings can't be changed in the new editor. The content in the body of the macro can be edited. |
Expected Results
The supported content is editable.
Actual Results
Supported macros content is uneditable
Workaround 1
If you've converted the page, restore it to the legacy page. More info on how to restore can be found here: https://support.atlassian.com/confluence-cloud/docs/create-edit-and-publish-a-page/#Page-versions-and-history.1
Manually edit the page and remove the supported macro content from the unsupported content before starting the conversion.
Workaround 2 - Preferred
Copy the macro displaying "confluenceADFMigrationUnsupportedContentInternalExtension" and paste it outside of the wrapper macro, then publish the page. This will enable the supported contents within the macro to be editable when the page is reaccessed.
Supported Macros
For a complete list of supported and unsupported macros, refer to https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/
- mentioned in
-
Page Loading...