Page History

Requirements

• You must have system administration privileges to install the theme
• You must have correctly set the Base URL in Confluence's General Configuration settings.

Should you encounter any problems, please see our Troubleshooting Guide which lists all common problems and how to fix them.

Plugin Requirements Overview

Confluence 1.4.x is no longer supported - you can try Builder 1.4 or 1.5 if desired. The Content Formatting and Page Information Tools plugins were not required for Builder 1.x.

Installing the Builder Plugin

If you are upgrading from an earlier version of Builder, please see the important notes on upgrading Builder later in this tutorial.

When manually downloading plugins using Internet Explorer, make sure the file extension isn't changed to ".zip" - if it is, change it back to ".jar" before installing the plugin.

1. Install Dependant Plugins

Theme Builder requires two open source plugins, both developed by Adaptavist, to be installed:

• Page Information Tools Plugin
• Content Formatting Macros

The easiest way to install these plugins is via the Plugin Repository. Alternatively you can download these plugins manually and install via the Plugin Manager or "Uploads" tab on the Plugin Repository.

Note: These plugins are only required for the navigation and title panels default settings - if you don't want to use tables or display page information in your customised theme design, you will not require these plugins.

2. Disable "Compatibility Macros" plugin

...or "incompatibility nightmares" as Adaptavist lovingly refer to them!

In the Plugin Manager, you'll see a plugin called "Compatibility Macros" - it's developed by Atlassian and is bundled with Confluence. It's enabled by default and sometimes also gets enabled after doing a Confluence upgrade in some circumstances, even if you've previously disabled or uninstalled it.

Unfortunately, the macros in this plugin break stuff - especially the table macro. Very few wikis actually need the plugin so generally we recommend disabling it completely. The main culprit is the table macro which can be disabled in isolation if desired.

If you have one of the very rare wikis that need the plugin, specifically the table macro, then you won't be able to use the macro of the same name from Adaptavist's free Content Formatting Macros plugin. The table macro is used primarily in the Header, Navigation and Title panels of the DEFAULT layout so you'd have to find some alternate way of arranging the content in those panels if you're unable to disable Atlassian's bundled Compatibility Macros plugin.

3. Install Theme Builder

Take a full backup of Confluence then follow the instructions applicable to the version of the Builder theme you are using as shown below:

4. Applying the Theme

Once the theme is installed, you need to apply it to spaces (or globally) for it to take effect. For more information, please see: Enabling the Theme.

Before your first use of the theme, you will have to accept the End User License Agreement - if you do not, most of the themes features will be disabled.

To customise the theme to your requirements, please see Theme Configuration.

Upgrading Theme Builder

Take a full backup of Confluence before upgrading Theme Builder or Confluence.

Before installing a new version of Theme Builder, the old version must first be uninstalled:

• If using the Plugin Repository to install the new version (including using the "Upload" tab), the old version will be automatically uninstalled
• If you uploaded via the Plugin Manager, first select the existing version of the plugin (by clicking the link in Plugin Manager) and click the "Uninstall Plugin" link to remove it
• If you manually installed the plugin to the WEB-INF/lib folder (not a good idea), you must manually delete that file from disk

Specific notes for various upgrade scenarios are shown below - click all that apply:

All currently known issues relating to upgrades of Theme Builder or Confluence are covered by our Builder Troubleshooting Guide.

Bug Reports and Feature Requests

Before reporting a bug, please check our Builder Troubleshooting Guide and Release Notes - it's possible a solution already exists or a recent version of the theme already resolves the issue you have.