Changes between Version 6 and Version 7 of TracUpgrade
- Timestamp:
- 07/28/2020 06:19:41 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracUpgrade
v6 v7 105 105 106 106 If other permission policies are enabled, `trac.ini` will need to have `ReadonlyWikiPolicy` appended to the list of active `permission_policies`. See TracFineGrainedPermissions#ReadonlyWikiPolicy for additional details on the proper ordering. 107 108 ===== Navigation Ordering Moved 109 110 The mainnav and metanav configuration ordering have 111 been moved from `[trac]` `mainnav` and `[trac]` `metanav` to the `[mainnav]` and `[metanav]` sections. The ordering is now specified using the `order` attribute as described in [TracNavigation#nav-order TracNavigation]. 112 113 The new configuration values will be written to trac.ini on upgrade, preserving the navigation order for the environment. You may need to edit trac.ini 114 if you use a shared [TracIni#GlobalConfiguration global configuration]. 115 For example, if you wish to specify the navigation ordering for several environments in `global.ini`, you'll 116 need to add the `[mainnav]` and `[metanav]` sections 117 in that file and delete those sections from each 118 environment's trac.ini. 107 119 108 120 ==== Upgrading from Trac 0.12 to Trac 1.0 #to1.0 … … 246 258 }}} 247 259 248 There are some significant caveats in this, such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state. So you will probably want to migrate to "basic" workflow; [trac:source: trunk/contrib/workflow/migrate_original_to_basic.py contrib/workflow/migrate_original_to_basic.py] may be helpful. See TracWorkflow for a detailed description of the new basic workflow.260 There are some significant caveats in this, such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state. So you will probably want to migrate to "basic" workflow; [trac:source:branches/1.2-stable/contrib/workflow/migrate_original_to_basic.py contrib/workflow/migrate_original_to_basic.py] may be helpful. See TracWorkflow for a detailed description of the new basic workflow. 249 261 250 262 === 7. Restart the Web Server #RestarttheWebServer … … 258 270 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 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. 259 271 260 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.272 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 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. 261 273 262 274 === !ZipImportError … … 281 293 === Upgrading Python 282 294 283 Upgrading Python to a newer version will require reinstallation of Python packages: Trac itself of course, but also [http ://pypi.python.org/pypi/setuptools easy_install], if you've been using that. If you are using Subversion, you'll also need to upgrade the Python bindings for svn.295 Upgrading Python to a newer version will require reinstallation of Python packages: Trac itself of course, but also [https://pypi.org/project/setuptools easy_install], if you've been using that. If you are using Subversion, you'll also need to upgrade the Python bindings for svn. 284 296 285 297 ==== Windows and Python 2.6 286 298 287 If you've been using !CollabNet's Subversion package, you may need to uninstall that in favor of [http ://alagazam.net/ Alagazam], which has the Python bindings readily available, see [trac:TracSubversion]. That package works without tweaking.299 If you've been using !CollabNet's Subversion package, you may need to uninstall that in favor of [https://alagazam.net/ Alagazam], which has the Python bindings readily available, see [trac:TracSubversion]. That package works without tweaking. 288 300 289 301 === Changing Database Backend