Changes between Version 88 and Version 89 of TracUpgrade

Timestamp:

Feb 26, 2011, 12:39:14 PM (13 years ago)

Author:

Christian Boos

Comment:

#CustomizedTemplates add a note about template customization and the need to rebase them on the newer version (#10041)

TracUpgrade

@@ -11 +11 @@
 === 1. Bring your server off-line
 
-It is not a good idea to update a running server: the server processes may have parts of the current packages cached in memory, and updating the code will likely trigger internal errors. 
+It is not a good idea to update a running server: the server processes may have parts of the current packages cached in memory, and updating the code will likely trigger [#ZipImportError internal errors]. 
 
 === 2. Update the Trac Code === #UpdatetheTracCode
@@ -141 +141 @@
 Things you should pay attention to, while upgrading.
 
+=== Customized Templates
+
+Trac supports customization of its Genshi templates by placing copies of the templates in the `<env>/templates` folder of your [TracEnvironment environment] or in a common location specified in the [[TracIni#GlobalConfiguration| [inherit] templates_dir]] configuration setting. If you choose to do so, be wary that you will need to repeat your changes manually on a copy of the new templates when you upgrade to a new release of Trac (even a minor one), as the templates will likely evolve. So keep a diff around ;-)
+
+The preferred way to perform TracInterfaceCustomization is to write a custom plugin doing an appropriate `ITemplateStreamFilter` transformation, as this is more robust in case of changes: we usually won't modify element `id`s or change CSS `class`es, and if we have to do so, this will be documented in the TracDev/ApiChanges pages.
+
 === !ZipImportError ===