| 11 | | It is not a good idea to update a running server: the server processes may have parts of the current packages cached in memory, and updating the code will likely trigger [#ZipImportError internal errors]. |
| 12 | | |
| 13 | | === 2. Update the Trac Code === #UpdatetheTracCode |
| | 11 | It is not a good idea to update a running server: the server processes may have parts of the current packages cached in memory, and updating the code will likely trigger [#ZipImportError internal errors]. |
| | 12 | |
| | 13 | Although a database backup will be implicitly created by default when upgrading the environment, it is always a good idea to perform a full backup of the environment using the [TracBackup hotcopy] command before beginning. |
| | 14 | |
| | 15 | === 2. Update the Trac Code #UpdatetheTracCode |
| 31 | | You may also want to remove the Trac `cgi-bin`, `htdocs`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac`. (The exact location depends on your platform.) |
| 32 | | |
| 33 | | This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as you won't waste your time looking at code or templates from a previous release that are not being used anymore... As usual, make a backup before actually deleting things. |
| 34 | | |
| 35 | | === 3. Upgrade the Trac Environment === #UpgradetheTracEnvironment |
| | 33 | You may also want to remove the Trac `cgi-bin`, `htdocs`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac`. The exact location depends on your platform. This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as your installation is uncluttered by code or templates from a previous release that is not used anymore. As usual, make a backup before actually removing things. |
| | 34 | |
| | 35 | === 3. Upgrade the Trac Environment #UpgradetheTracEnvironment |
| 75 | | === 6. Steps specific to a given Trac version === |
| 76 | | ==== Upgrading from Trac 0.12 to Trac 1.0 ==== #to1.0 |
| 77 | | |
| | 74 | === 6. Steps specific to a given Trac version |
| | 75 | |
| | 76 | ==== Upgrading from Trac 1.0 to 1.1.x #to1.1.x |
| | 77 | |
| | 78 | ===== Python 2.5 no longer supported |
| | 79 | Upgrade Python to at least 2.6, but not 3.0. |
| | 80 | |
| | 81 | ===== New workflow actions |
| | 82 | |
| | 83 | The ticket creation step is now 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. |
| | 84 | |
| | 85 | ===== New permissions policy for read-only wiki pages |
| | 86 | 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: |
| | 87 | {{{#!ini |
| | 88 | [trac] |
| | 89 | permission_policies = ReadonlyWikiPolicy, |
| | 90 | DefaultPermissionPolicy, |
| | 91 | LegacyAttachmentPolicy |
| | 92 | }}} |
| | 93 | 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. |
| | 94 | |
| | 95 | ==== Upgrading from Trac 0.12 to Trac 1.0 #to1.0 |
| | 96 | |
| | 97 | ===== Python 2.4 no longer supported |
| | 98 | Upgrade Python to at least 2.5, but not 3.0. |
| | 99 | |
| | 100 | ===== Subversion components not enabled by default for new installations |
| 85 | | Another step in the automatic upgrade will change the way the attachments are stored. If you're a bit paranoid, you might want to take a backup of the `attachments` directory before upgrading (but if you are, you already did a full copy of the environment, no?). 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 go have a look to these files, move them elsewhere and remove the `attachments` directory manually to cleanup the environment. The attachments themselves are now all located in your environment below the `files/attachments` directory. |
| 86 | | |
| 87 | | |
| 88 | | ==== Upgrading from Trac 0.11 to Trac 0.12 ==== |
| 89 | | |
| 90 | | ===== Python 2.3 no longer supported ===== |
| 91 | | The minimum supported version of python is now 2.4 |
| 92 | | |
| 93 | | ===== SQLite v3.x required ===== |
| | 108 | ===== Attachments migrated to new location |
| | 109 | 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. |
| | 110 | |
| | 111 | ===== Behavior of `[ticket] default_owner` changed |
| | 112 | 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. |
| | 113 | |
| | 114 | ==== Upgrading from Trac 0.11 to Trac 0.12 |
| | 115 | |
| | 116 | ===== Python 2.3 no longer supported |
| | 117 | The minimum supported version of Python is now 2.4. |
| | 118 | |
| | 119 | ===== SQLite v3.x required |
| 102 | | This may be of interest to users with only one repository, since there's now a way to avoid the potentially costly resync check at every request. |
| 103 | | |
| 104 | | ===== Resynchronize the Trac Environment Against the Source Code Repository ===== |
| 105 | | |
| 106 | | Each [TracEnvironment Trac environment] must be resynchronized against the source code repository in order to avoid errors such as "[http://trac.edgewall.org/ticket/6120 No changeset ??? in the repository]" while browsing the source through the Trac interface: |
| 107 | | |
| 108 | | {{{ |
| | 128 | This may be of interest to users with only one repository, since there is now a way to avoid the potentially costly resync check at every request. |
| | 129 | |
| | 130 | ===== Resynchronize the Trac Environment Against the Source Code Repository |
| | 131 | |
| | 132 | Each [TracEnvironment Trac environment] must be resynchronized against the source code repository in order to avoid errors such as "[trac:#6120 No changeset ??? in the repository]" while browsing the source through the Trac interface: |
| | 133 | |
| | 134 | {{{#!sh |
| 119 | | ===== Authz permission checking ===== |
| 120 | | 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). |
| 121 | | |
| 122 | | ===== Microsecond timestamps ===== |
| 123 | | 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. |
| 124 | | |
| 125 | | ==== Upgrading from Trac 0.10 to Trac 0.11 ==== |
| 126 | | ===== Site Templates and Styles ===== |
| | 145 | ===== Authz permission checking |
| | 146 | 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. |
| | 147 | |
| | 148 | ===== Microsecond timestamps |
| | 149 | 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. |
| | 150 | |
| | 151 | ==== Upgrading from Trac 0.10 to Trac 0.11 |
| | 152 | ===== Site Templates and Styles |
| 129 | | If you are using custom CSS styles or modified templates in the `templates` directory of the TracEnvironment, you will need to convert them to the Genshi way of doing things. To continue to use your style sheet, follow the instructions at TracInterfaceCustomization#SiteAppearance. |
| 130 | | |
| 131 | | ===== Trac Macros, Plugins ===== |
| 132 | | 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. |
| 133 | | |
| 134 | | ===== For FCGI/WSGI/CGI users ===== |
| | 155 | If you are using custom CSS or modified templates in the `templates` directory of the TracEnvironment, you will need to convert them to the Genshi way of doing things. To continue to use your style sheet, follow the instructions at TracInterfaceCustomization#SiteAppearance. |
| | 156 | |
| | 157 | ===== Trac Macros, Plugins |
| | 158 | 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. |
| | 159 | |
| | 160 | ===== For FCGI/WSGI/CGI users |
| 142 | | ===== Web Admin plugin integrated ===== |
| 143 | | If you had the webadmin plugin installed, you can uninstall it as it is part of the Trac code base since 0.11. |
| 144 | | |
| 145 | | === 7. Restart the Web Server === #RestarttheWebServer |
| | 168 | ===== Web Admin plugin integrated |
| | 169 | If you had the [trac:WebAdmin] plugin installed, you can uninstall it as it is part of the Trac code base since 0.11. |
| | 170 | |
| | 171 | ===== New Default Configurable Workflow |
| | 172 | |
| | 173 | 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. |
| | 174 | |
| | 175 | Graphically, that looks like this: |
| | 176 | |
| | 177 | {{{#!Workflow width=500 height=240 |
| | 178 | leave = * -> * |
| | 179 | leave.operations = leave_status |
| | 180 | leave.default = 1 |
| | 181 | accept = new -> assigned |
| | 182 | accept.permissions = TICKET_MODIFY |
| | 183 | accept.operations = set_owner_to_self |
| | 184 | resolve = new,assigned,reopened -> closed |
| | 185 | resolve.permissions = TICKET_MODIFY |
| | 186 | resolve.operations = set_resolution |
| | 187 | reassign = new,assigned,reopened -> new |
| | 188 | reassign.permissions = TICKET_MODIFY |
| | 189 | reassign.operations = set_owner |
| | 190 | reopen = closed -> reopened |
| | 191 | reopen.permissions = TICKET_CREATE |
| | 192 | reopen.operations = del_resolution |
| | 193 | }}} |
| | 194 | |
| | 195 | 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. |
| | 196 | |
| | 197 | === 7. Restart the Web Server #RestarttheWebServer |
| 155 | | 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 wary 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 ;-) |
| 156 | | |
| 157 | | 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 TracDev/ApiChanges pages. |
| 158 | | |
| 159 | | === !ZipImportError === |
| 160 | | |
| 161 | | Due to internal caching of zipped packages, whenever the content of the packages change on disk, the in-memory zip index will no longer match and you'll get irrecoverable !ZipImportError errors. Better anticipate and bring your server down for maintenance before upgrading. |
| | 205 | 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. |
| | 206 | |
| | 207 | 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. |
| | 208 | |
| | 209 | === !ZipImportError |
| | 210 | |
| | 211 | Due to internal caching of zipped packages, whenever the content of the packages change on disk, the in-memory zip index will no longer match and you'll get irrecoverable !ZipImportError errors. Better anticipate and bring your server down for maintenance before upgrading. |
| 167 | | === Trac database upgrade === |
| 168 | | |
| 169 | | A known issue in some versions of PySqlite (2.5.2-2.5.4) prevents the trac-admin upgrade script from successfully upgrading the database format. It is advised to use either a newer or older version of the sqlite python bindings to avoid this error. For more details see ticket [trac:#9434]. |
| 170 | | |
| 171 | | === parent dir === |
| 172 | | If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work. |
| | 217 | === Trac database upgrade |
| | 218 | |
| | 219 | A known issue in some versions of [trac:PySqlite] (2.5.2-2.5.4) prevents the trac-admin upgrade script from successfully upgrading the database format. It is advised to use either a newer or older version of the sqlite python bindings to avoid this error. For more details see ticket [trac:#9434]. |
| | 220 | |
| | 221 | === Parent dir |
| | 222 | 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. |
| 176 | | === Upgrading Python === |
| 177 | | |
| 178 | | Upgrading Python to a newer version will require reinstallation of Python packages: Trac of course; also [http://pypi.python.org/pypi/setuptools easy_install], if you've been using that. Assuming you're using Subversion, you'll also need to upgrade the Python bindings for svn. |
| 179 | | |
| 180 | | ==== Windows and Python 2.6 ==== |
| 181 | | |
| 182 | | 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 TracSubversion). The good news is, that works with no tweaking. |
| 183 | | |
| 184 | | === Changing Database Backend === |
| 185 | | ==== SQLite to PostgreSQL ==== |
| 186 | | |
| 187 | | The [http://trac-hacks.org/wiki/SqliteToPgScript sqlite2pg] script on [http://trac-hacks.org trac-hacks.org] has been written to assist in migrating a SQLite database to a PostgreSQL database |
| 188 | | |
| 189 | | === Upgrading from older versions of Trac === #OlderVersions |
| | 226 | === Upgrading Python |
| | 227 | |
| | 228 | 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. |
| | 229 | |
| | 230 | ==== Windows and Python 2.6 |
| | 231 | |
| | 232 | 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. |
| | 233 | |
| | 234 | === Changing Database Backend |
| | 235 | |
| | 236 | 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. |
| | 237 | |
| | 238 | === Upgrading from older versions of Trac #OlderVersions |
