Confluence 2.5.6 : Upgrading Custom Layouts
This page last changed on Jul 10, 2007 by mjensen.
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.
Care must be taken on each new release of Confluence to reapply your changes to the new default templates. To reapply your custom layouts, you need to:
Obtaining Your Custom LayoutsBefore Confluence 2.3, custom layouts are stored in the velocity directory within your Conflunce home directory tree. You can open these files in any text editor. With Confluence 2.3 and after, 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. Reapply Your CustomisationsYou 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.
|
![]() |
Document generated by Confluence on Oct 10, 2007 18:36 |