Changes between Version 21 and Version 22 of 1.1/TracUpgrade
- Timestamp:
- Jun 22, 2016, 10:57:16 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
1.1/TracUpgrade
v21 v22 41 41 }}} 42 42 43 This command will do nothingif the environment is already up-to-date.43 This command will not have any effect if the environment is already up-to-date. 44 44 45 45 Note that a backup of your database will be performed automatically prior to the upgrade. 46 This feature is relatively new for PostgreSQL or MySQL databases, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade , run:46 This feature is relatively new for PostgreSQL or MySQL databases, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade: 47 47 {{{#!sh 48 48 trac-admin /path/to/projenv upgrade --no-backup … … 64 64 trac-admin /path/to/env deploy /deploy/path 65 65 }}} 66 this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. 66 67 This will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. 67 68 68 69 Some web browsers (IE, Opera) cache CSS and Javascript files aggressively, so you may need to instruct your users to manually erase the contents of their browser's cache, a forced refreshed (`<F5>`) should be enough. … … 76 77 77 78 ===== Python 2.5 no longer supported 79 78 80 Upgrade Python to at least 2.6 or 2.7, but not 3.0 or greater. 79 81 80 82 ===== Obsolete Plugins 83 81 84 Trac has added functionality equivalent to the following plugins: 82 85 * [https://trac-hacks.org/wiki/AdminEnumListPlugin AdminEnumListPlugin] … … 92 95 ===== New workflow actions #NewWorkflowActions 93 96 94 The ticket creation step is nowcontrolled with a workflow action. The default workflow has `create` and `create_and_assign` actions. The `create` action will always be added when upgrading the database. The `create_and_assign` action will be added if the workflow has an //assigned// state. You may want to edit your workflow after upgrading the database to customize the actions available on the //New Ticket// page.97 The ticket creation step is controlled with a workflow action. The default workflow has `create` and `create_and_assign` actions. The `create` action will always be added when upgrading the database. The `create_and_assign` action will be added if the workflow has an //assigned// state. You may want to edit your workflow after upgrading the database to customize the actions available on the //New Ticket// page. 95 98 96 99 ===== New permissions policy for read-only wiki pages 100 97 101 Since 1.1.2 the read-only attribute of wiki pages is enabled and enforced only when `ReadonlyWikiPolicy` is in the list of active permission policies. If `[trac] permission_policy` has the default value `DefaultPermissionPolicy, LegacyAttachmentPolicy`, then `ReadonlyWikiPolicy` should be automatically appended to the list when upgrading the environment: 98 102 {{{#!ini … … 102 106 LegacyAttachmentPolicy 103 107 }}} 104 If other permission policies are enabled, //trac.ini// will need to be edited to append `ReadonlyWikiPolicy` to the list of active `permission_policies`. See TracFineGrainedPermissions#ReadonlyWikiPolicy for additional details on the proper ordering. 108 109 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. 105 110 106 111 ==== Upgrading from Trac 0.12 to Trac 1.0 #to1.0 107 112 108 113 ===== Python 2.4 no longer supported 114 109 115 Upgrade Python to at least 2.5, but not 3.0. 110 116 … … 120 126 121 127 ===== Subversion components not enabled by default for new installations 128 122 129 The Trac components for Subversion support are no longer enabled by default. To enable the svn support, you need to make sure the `tracopt.versioncontrol.svn` components are enabled, for example by setting the following in the TracIni: 123 130 {{{#!ini … … 125 132 tracopt.versioncontrol.svn.* = enabled 126 133 }}} 134 127 135 The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled. 128 136 129 137 ===== Attachments migrated to new location 138 130 139 Another step in the automatic upgrade will change the way the attachments are stored. Create a backup of the `attachments` directory before upgrading. In case the `attachments` directory contains some files which are //not// attachments, the last step of the migration to the new layout will fail: the deletion of the now unused `attachments` directory can't be done if there are still files and folders in it. You may ignore this error, but better to move them elsewhere and remove the `attachments` directory manually. The attachments themselves are now all located in your environment below the `files/attachments` directory. 131 140 132 141 ===== Behavior of `[ticket] default_owner` changed 142 133 143 Prior to 1.0, the owner field of new tickets always defaulted to `[ticket] default_owner` when the value was not empty. If the value was empty, the owner field defaulted to to the Component's owner. In 1.0 and later, the `default_owner` must be set to `< default >` to make new tickets default to the Component's owner. This change allows the `default_owner` to be set to an empty value if no default owner is desired. 134 144 … … 136 146 137 147 ===== Python 2.3 no longer supported 148 138 149 The minimum supported version of Python is now 2.4. 139 150 140 151 ===== SQLite v3.x required 152 141 153 SQLite v2.x is no longer supported. If you still use a Trac database of this format, you'll need to convert it to SQLite v3.x first. See [trac:PySqlite#UpgradingSQLitefrom2.xto3.x] for details. 142 154 143 155 ===== [trac:PySqlite] 2 required 156 144 157 [trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below. 145 158 … … 160 173 161 174 ===== Multiple Repository Support 175 162 176 The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration. 163 177 … … 173 187 174 188 ===== Improved repository synchronization 189 175 190 In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories. 176 191 … … 180 195 181 196 ===== Authz permission checking 197 182 198 The authz permission checking has been migrated to a fine-grained permission policy. If you use authz permissions (aka `[trac] authz_file` and `authz_module_name`), you must add `AuthzSourcePolicy` in front of your permission policies in `[trac] permission_policies`. You must also remove `BROWSER_VIEW`, `CHANGESET_VIEW`, `FILE_VIEW` and `LOG_VIEW` from your global permissions with `trac-admin $ENV permission remove` or the "Permissions" admin panel. 183 199 184 200 ===== Microsecond timestamps 201 185 202 All timestamps in database tables, except the `session` table, have been changed from "seconds since epoch" to "microseconds since epoch" values. This change should be transparent to most users, except for custom reports. If any of your reports use date/time columns in calculations (e.g. to pass them to `datetime()`), you must divide the values retrieved from the database by 1'000'000. Similarly, if a report provides a calculated value to be displayed as a date/time (i.e. with a column named "time", "datetime", "changetime", "date", "created" or "modified"), you must provide a microsecond timestamp, that is, multiply your previous calculation with 1'000'000. 186 203 187 204 ==== Upgrading from Trac 0.10 to Trac 0.11 205 188 206 ===== Site Templates and Styles 207 189 208 The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information. 190 209 … … 192 211 193 212 ===== Trac Macros, Plugins 213 194 214 The Trac macros will need to be adapted, as the old-style wiki-macros are not supported anymore due to the drop of [trac:ClearSilver] and the HDF. They need to be converted to the new-style macros, see WikiMacros. When they are converted to the new style, they need to be placed into the plugins directory instead and not wiki-macros, which is no longer scanned for macros or plugins. 195 215 196 216 ===== For FCGI/WSGI/CGI users 217 197 218 For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file: 198 219 {{{#!sh … … 203 224 204 225 ===== Web Admin plugin integrated 226 205 227 If you had the [trac:WebAdmin] plugin installed, you can uninstall it as it is part of the Trac code base since 0.11. 206 228 207 229 ===== New Default Configurable Workflow 208 230 209 When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10. 210 211 Graphically, that looks like this: 231 When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10: 212 232 213 233 {{{#!Workflow width=500 height=240 … … 249 269 250 270 === Wiki Upgrade 271 251 272 `trac-admin` will not delete or remove default wiki pages that were present in a previous version but are no longer in the new version. 252 273 … … 256 277 257 278 === Parent dir 279 258 280 If you use a Trac parent env configuration and one of the plugins in one child does not work, none of the children will work. 259 281 … … 270 292 === Changing Database Backend 271 293 272 The [http ://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin] on [http://trac-hacks.org trac-hacks.org] has been written to assist in migrating between SQLite, MySQL and PostgreSQL databases.294 The [https://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin] on [https://trac-hacks.org trac-hacks.org] has been written to assist in migrating between SQLite, MySQL and PostgreSQL databases. 273 295 274 296 === Upgrading from older versions of Trac #OlderVersions