...
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
The instructions are divided into two parts: understand how many pages and/or templates need updation, and run the actual updation process. The first part merely allows administrators to keep a check on any errors or mismatches in the number of updates made in the second part.
To know how many pages and/or templates in your instance require the HTML macro name update:
...
| Tip | ||
|---|---|---|
| ||
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.
Tip title 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.
Note 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.
...