Migrating from ThemeBuilder 4 to ThemeBuilder 5
In ThemeBuilder 5 onwards, the format of the skin data and backup files changed significantly from ThemeBuilder 4. These data and backup files from version 4 back are not compatible with the newer versions of ThemeBuilder.
We have made a layout exporter available to reduce the work involved in importing compatible layout data for ThemeBuilder 5. The layout exporter generates a skin that replicates the original and converts much of the old menu markup to ThemeBuilder compatible macros.
Menu Macros
If you want to migrate a theme and retain all existing menu macros, please follow these instructions and use the free Hmenu Legacy Plugin. Make sure to note the important information on that page, as this is a free, unsupported plugin and is only supplied as an interim measure until your developers have migrated all menus over to the new Confluence 5 format.
Exporter Instructions for a Full Migration
Notes
If your Confluence 5 server:
- HAS NOT been used for a ThemeBuilder migration
or
- DOES NOT have ThemeBuilder or the Exporter installed
follow all steps as described in the instructions below.
If your Confluence 5 server:
- HAS been used for a ThemeBuilder migration
or
- DOES have ThemeBuilder or the Exporter installed
you need to overwrite this theme.
If your Confluence 5 server:
- HAS been used for a ThemeBuilder migration
or
- DOES have ThemeBuilder or the Exporter installed
you should keep this theme.
Adaptavist does not recommend running multiple migrations on the same server. If you want to maintain the existing theme, then be sure to select the Merge Uploaded Layout Data with Existing Layouts checkbox in steps 2 and 6.
Instructions for a Confluence 4 Server Upgraded to Confluence 5
Follow these instructions to export your existing layouts as a Skin Backup that can be uploaded into ThemeBuilder. On your Confluence 5 server that has been upgraded from Confluence 4:
Once the Skin Backup has been uploaded, you may use the Skin Editor to view the exported layout. If you are satisfied that your layouts have been migrated successfully to skins, you may uninstall the exporter.
Converted Skins
Exported layouts will consist of a Main panel replicating the old ThemeBuilder theme structure. You should not need to edit this panel since it only exists to provide the framework for your panel content. The Dashboard panel will contain the contents of your dashboard.wiki resource. Similarly, the Flaglogic panel will have the contents of the flaglogic.wiki resource.
Notice that the storage format panels inherited from the root skin are disabled. This is intentional because they are no longer used within an exported layout. Instead, panels have been created to match those used by the original layout, the wiki markup that they contained has been copied over, and the menu items translated into ThemeBuilder compatible macros where possible.
An exported layout will not be immediately usable since ThemeBuilder uses the internal Confluence menu functionality to generate the drop-down menu areas. This adds some complexity to re-using an exported layout since the Atlassian menu code is not capable of generating nested menus. We suggest reviewing menu usage for this task. See the section on ThemeBuilder Menus for more help with this.