This article contains information about migrating HTML macro content from server to cloud. For existing customers, migrating content of the HTML for Confluence HTML macro to cloud was discouraged due to certain Atlassian Confluence cloud limitations as listed in the HTML-362 Jira issue. Due to this issue, it was possible to have issues in rendering HTML content on pages and/or templates that used the HTML macro of the HTML for Confluence app.
With the introduction of the HTML macro name update process, the macro name is now updated from HTML to HTML-Bobswift for all pages and/or templates.
Issues about mismatching HTML macro names are thus resolved, and administrators can complete their migration process from server to cloud without any HTML content display issues. This article contains the relevant information required to make a seamless transition of HTML content from server to cloud.
Instructions
To know how many pages and/or templates in your instance require the HTML macro name update:
- Select
> Administration > Macro usage, or search for Macro usage. - Scroll down to Bob Swift Atlassian Apps - HTML and see the number of pages mentioned for the html entry.
This is the number of pages and/or templates that require the HTML macro name change.
How to confirm if all pages and/or templates are updated?
After this updation process is completed, you can revisit the Macro usage page to verify that all the required pages and/or templates that use the HTML macro are updated.
To update the macro name from HTML to HTML-Bobswift for your instance:
- Select > Manage apps.
Either search for HTML for Confluence or scroll to Bob Swift Configuration, and click HTML to view app configuration.
Try this for older Confluence versions!
Navigate to CONFLUENCE ADMINISTRATION > Settings > ATLASSIAN MARKETPLACE > HTML.
This opens the HTML for Confluence Configuration page.
- Select <tab name>. This tab displays some information about the HTML macro usage in your instance similar to the following screenshot:
<screenshot> Click Update pages to start the updation process.
Leaving this page does not disrupt the updation process as it runs in the background.
This process can be run as many times as required.
Every page or template that is processed shows up as an update in Page history.
After the updation process is completed, the macro usage information on the page is updated and these updates can be verified through the Macro usage page as mentioned in the previous section.
It is recommended to run the Confluence Migration Assistant to complete the migration process from server to cloud. This is because the updation process does not actually migrate the HTML contents, but simply resolves the mismatch of the HTML macro names used in server and cloud.
