Changes between Version 16 and Version 17 of 1.3/TracUpgrade

Timestamp:

Jun 22, 2017, 6:37:29 AM (7 years ago)

Author:

Ryan J Ollos

Comment:

Merge TracUpgrade@127.

1.3/TracUpgrade

@@ -227 +227 @@
 Trac supports customization of its 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 aware 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 a custom plugin doing client-side JavaScript transformation of the generated output, 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 [trac:TracDev/ApiChanges] pages.
+The preferred way to perform TracInterfaceCustomization is a custom plugin doing client-side JavaScript transformation of the generated output, as this is more robust in case of changes: we usually won't modify an element `id` or change its CSS `class`, and if we have to do so, this will be documented in the [trac:TracDev/ApiChanges] pages.
 
 === !ZipImportError