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! |
Confluence の新しいリリースではそれぞれ、新しい既定テンプレートに対して行った変更を再適用してください。
カスタム レイアウトを最適用するために必要なものは、次のとおりです。
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.
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.
Velocity はテンプレートをメモリにキャッシュするように設定されています。Confluence 内からページを編集する場合、そのページをディスクからリロードします。ディスク上のページを編集する場合、WEB-INF/classes/velocity.properties で Velocity のキャッシングを一時的にオフにするか、変更を可視化するためにサーバを再起動する必要があります。
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:
|
Because we only officially support the modification of the three global decorator files, other 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. |