Edgewall Software

Changes between Version 126 and Version 127 of TracUpgrade


Ignore:
Timestamp:
Jun 22, 2017, 6:35:21 AM (5 months ago)
Author:
Ryan J Ollos
Comment:

Modify markup that doesn't export to ReST without errors.

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v126 v127  
    259259Trac 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 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.
    260260
    261 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 [trac:TracDev/ApiChanges] pages.
     261The 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 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.
    262262
    263263=== !ZipImportError