Changes between Version 30 and Version 31 of 1.3/TracUpgrade

Timestamp:

Aug 20, 2019, 11:12:00 PM (5 years ago)

Author:

Ryan J Ollos

Comment:

Fix formatting issues in ReST conversion. Refs #12835.

1.3/TracUpgrade

@@ -103 +103 @@
 * [https://trac-hacks.org/wiki/NavAddPlugin NavAddPlugin]: see TracNavigation
 * [https://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignToPlugin]: subclass `ConfigurableTicketWorkflow` and override `get_allowed_owners`
-* [https://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin]: Use TracAdmin `convert_db`  command
+* [https://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin]: Use the `trac-admin` [TracAdmin#ChangingDatabaseBackend convert_db command]
 
 The plugins should be removed when upgrading Trac to 1.4.
@@ -109 +109 @@
 ===== Jinja2 is the new template engine
 
-In Trac itself, all the content is now generated by using the Jinja2 template engine.
-You may want to verify that your plugins are compatible with this change.
+Content is now generated by using the Jinja2 template
+engine. You may want to verify that your plugins are
+compatible with this change.
 (TODO: expand...)
 
-If you customized the Trac templates, or the site.html template, you'll need to adapt that as well.
+If you customized the Trac templates, or the `site.html` 
+template, you'll need to adapt that as well.
 (TODO: expand...) See [#CustomizedTemplates]
 
@@ -224 +226 @@
 ==== Upgrading from older versions of Trac #OlderVersions
 
-For upgrades from versions older than Trac 0.12, refer first to [trac:wiki:0.12/TracUpgrade#SpecificVersions].
-
-For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions].
+For upgrades from versions older than Trac 0.12, refer first to [trac:wiki:0.12/TracUpgrade#SpecificVersions TracUpgrade for 0.12].
+
+For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions TracUpgrade for 0.10].
 
 == Known Issues
@@ -232 +234 @@
 === Customized Templates
 
-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 customize the templates, be aware that you will need to repeat your changes on a copy of the new templates when you upgrade to a new release of Trac (even a minor one), as the templates will evolve. So keep a diff around.
+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 customize the templates, be aware that you will need to repeat your changes on a copy of the new templates when you upgrade to a new release of Trac (even a minor one), as the templates will 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 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.