Confluence Docs 3.0 : Upgrading Custom Layouts This page last changed on Jun 13, 2008 by jlargman. As Confluence evolves, so do the default layouts that drive the rendering of every page. As new functionality is added or current functionally is changed, the default layouts are modified to support these changes.
| If you are using custom layouts based on defaults from a previous Confluence version, you run the risk of breaking functionality, or worse, missing out on great new features!
Take care on each new release of Confluence to reapply your changes to the new default templates. To reapply your custom layouts, you need to: Obtain the source of your custom layout from your current version of Confluence. Reapply your customisations to the new default layouts. ## Step 1. Obtaining your Custom Layouts Before Confluence 2.3, custom layouts are stored in the `velocity` directory within your Confluence home directory tree. You can open these files in any text editor. With Confluence 2.3 and later, custom layouts are stored in the `DECORATOR` table within your Confluence database. You can `SELECT` for the source of the layout using SQL like this:
    mysql> select SPACEKEY,DECORATORNAME,BODY from DECORATOR;
    +----------+---------------------+------+
    | SPACEKEY | DECORATORNAME       | BODY |
    +----------+---------------------+------+
    | NULL     | decorators/main.vmd | ...  |
    +----------+---------------------+------+
    1 row in set (0.03 sec)
This example was tested on MySQL, but should be relevant for all SQL databases. ## Step 2. Reapplying your Customisations You will need to manually apply the changes you made to the new default layouts provided by the new version of Confluence. Use the documentation on customising layouts to create a new custom layout and use the source obtained in step 1 to manually reintegrate them. #### Turning off caching Velocity is configured to cache templates in memory. When you edit a page from within Confluence, it knows to reload that page from disk. If you are editing the pages on disk, you will either have to turn off velocity's caching temporarily in `WEB-INF/classes/velocity.properties`, or restart the server to make your changes visible. For Confluence 2.6, the `velocity.properties` file is available in the `confluence-2.6.0.jar` file. The jar file is located in the `WEB-INF/lib` directory. If you wish to make modification to the files in the jar, we recommend the following steps: Stop Confluence. Make a backup copy of the jar file. Un-jar the file Locate and edit the appropriate file that you wish to modify. Re-jar the confluence-2.6.0.jar file. Relocate the jar file to the appropriate directory. Restart Confluence.
| Test your modifications carefully Changes may interact unpredictably with future versions of Confluence. When upgrading, you should always test your custom modifications thoroughly before deploying them on a live site. It's beyond the scope of Atlassian Support to test and deploy these changes.

Document generated by Confluence on Nov 05, 2009 23:27