Changes between Version 17 and Version 18 of 1.3/TracUpgrade
- Timestamp:
- Jul 31, 2017, 7:05:13 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
1.3/TracUpgrade
v17 v18 14 14 If you are upgrading to a minor release, plugin compatibility is usually not a concern because the Trac API typically does not change, and major features are not introduced, for minor releases. 15 15 16 If your plugins are installed from [https://trac-hacks.org trac-hacks.org] you can check compatibility by looking for a tag on the project page corresponding to a major release (e.g. `1.2`). If you are unsure, you'll want to contact the plugin author or ask on the MailingList.16 If your plugins are installed from [https://trac-hacks.org trac-hacks.org] you can check compatibility by looking for a tag on the project page corresponding to a major release (e.g. `1.2`). If you are unsure, you'll want to contact the plugin author or ask on the [trac:MailingList MailingList]. 17 17 18 18 If you are running several Trac plugins it is good to test the upgrade and site functionality in a staging instance of your site before upgrading your production instance. Remember, plugin authors are responsible for Trac version compatibility and plugins can interact in unexpected ways. Your Trac instance may have a unique combination of plugins and therefore it's a good idea to do some verification testing when making any changes to your site. … … 76 76 77 77 {{{#!div style="border: 1pt dotted; margin: 1em" 78 **Note:** Some web browsers (IE, Opera) cache CSS and Javascript files, so you should instruct your users to manually erase the contents of their browser's cache. A forced refreshed (SHIFT + <F5>) should be sufficient.78 **Note:** Some web browsers (IE, Opera) cache CSS and !JavaScript files, so you should instruct your users to manually erase the contents of their browser's cache. A forced refreshed (SHIFT + <F5>) should be sufficient. 79 79 {{{#!comment 80 80 Remove above note once #9936 is fixed. … … 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. 228 228 229 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.229 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. 230 230 231 231 === !ZipImportError