| 4 | | A [TracEnvironment Trac environment] needs to be upgraded before it can be used with Trac 0.11. This document describes the steps necessary to upgrade an environment. |
| | 4 | == Instructions == |
| | 5 | |
| | 6 | Typically, there are seven steps involved in upgrading to a newer version of Trac: |
| | 7 | |
| | 8 | === 1. Update the Trac Code === #UpdatetheTracCode |
| | 9 | |
| | 10 | Get the new version as described in TracInstall, or your operating system specific procedure. |
| | 11 | |
| | 12 | If you already have a 0.11 version of Trac installed via `easy_install`, it might be easiest to also use `easy_install` to upgrade your Trac installation: |
| | 13 | |
| | 14 | {{{ |
| | 15 | # easy_install --upgrade Trac==0.12 |
| | 16 | }}} |
| | 17 | |
| | 18 | If you do a manual (not operating system-specific) upgrade, you should also stop any running Trac servers before the installation. Doing "hot" upgrades is not advised, especially on Windows ([trac:#7265]). |
| | 19 | |
| | 20 | You may also want to remove the pre-existing Trac code by deleting the `trac` directory from the Python `lib/site-packages` directory, or remove Trac `.egg` files from former versions. |
| | 21 | The location of the site-packages directory depends on the operating system and the location in which Python was installed. However, the following locations are typical: |
| | 22 | * on Linux: `/usr/lib/python2.X/site-packages` |
| | 23 | * on Windows: `C:\Python2.X\lib\site-packages` |
| | 24 | * on MacOSX: `/Library/Python/2.X/site-packages` |
| | 25 | |
| | 26 | 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.) |
| | 27 | |
| | 28 | 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. |
| | 29 | |
| | 30 | === 2. Upgrade the Trac Environment === #UpgradetheTracEnvironment |
| 7 | | |
| 8 | | |
| 9 | | == Instructions == |
| 10 | | |
| 11 | | Typically, there are four steps involved in upgrading to a newer version of Trac: |
| 12 | | |
| 13 | | === Update the Trac Code === |
| 14 | | |
| 15 | | Get the new version as described in TracInstall, or your operation system specific procedure. |
| 16 | | |
| 17 | | If you do a manual (not operating system specific) upgrade, you may also later on want to remove the existing Trac code by deleting the `trac` directory from the Python `lib/site-packages` directory. |
| 18 | | |
| 19 | | The location of the site-packages directory depends on the operating system, and the location in which Python was installed. However, the following locations are common: |
| 20 | | * If you’re using Linux: /usr/lib/python2.X/site-packages |
| 21 | | * If you’re using Windows: C:\Python2.X\lib\site-packages |
| 22 | | * If you’re using MacOSX: /Library/Python2.X/site-packages |
| 23 | | |
| 24 | | 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). |
| 25 | | |
| 26 | | > If you had the webadmin plugin installed, you can now uninstall it as it is now part of the Trac code base. |
| 27 | | |
| 28 | | |
| 29 | | === Upgrade the Trac Environment === |
| 56 | | === Restart the Web Server === |
| | 60 | {{{ |
| | 61 | trac-admin /path/to/projenv repository resync '*' |
| | 62 | }}} |
| | 63 | |
| | 64 | === 5. Refresh static resources === |
| | 65 | |
| | 66 | If you have set up a web server to give out static resources directly (accessed using the `/chrome/` URL) then you will need to refresh them using the same command: |
| | 67 | {{{ |
| | 68 | trac-admin /path/to/env deploy /deploy/path |
| | 69 | }}} |
| | 70 | this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. |
| | 71 | |
| | 72 | Some web browsers cache CSS and Javascript files persistently, so you may need to instruct your users to manually erase the contents of their browser's cache. |
| | 73 | |
| | 74 | === 6. Steps specific to a given Trac version === |
| | 75 | ==== Upgrading from Trac 0.11 to Trac 0.12 ==== |
| | 76 | ===== Python 2.3 no longer supported ===== |
| | 77 | The minimum supported version of python is now 2.4 |
| | 78 | |
| | 79 | ===== SQLite v3.x required ===== |
| | 80 | 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. |
| | 81 | |
| | 82 | ===== PySqlite 2 required ===== |
| | 83 | PySqlite 1.1.x is no longer supported. Please install 2.5.5 or later if possible (see [#Tracdatabaseupgrade Trac database upgrade] below). |
| | 84 | |
| | 85 | ===== Multiple Repository Support ===== |
| | 86 | The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration. |
| | 87 | |
| | 88 | 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. |
| | 89 | |
| | 90 | ===== Improved repository synchronization ===== |
| | 91 | In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories. |
| | 92 | |
| | 93 | While you can keep the same synchronization as in 0.11 adding the post-commit hook as outlined in TracRepositoryAdmin#Synchronization and TracRepositoryAdmin#ExplicitSync will allow more efficient synchronization and is more or less required for multiple repositories. |
| | 94 | |
| | 95 | Note that if you were using the `trac-post-commit-hook`, ''you're strongly advised to upgrade it'' to the new hook documented in the above references, as the old hook will not work with anything else than the default repository and even for this case, it won't trigger the appropriate notifications. |
| | 96 | |
| | 97 | ===== Authz permission checking ===== |
| | 98 | 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). |
| | 99 | |
| | 100 | ===== Microsecond timestamps ===== |
| | 101 | 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. |
| | 102 | |
| | 103 | ==== Upgrading from Trac 0.10 to Trac 0.11 ==== |
| | 104 | ===== Site Templates and Styles ===== |
| | 105 | The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information. |
| | 106 | |
| | 107 | 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. |
| | 108 | |
| | 109 | ===== Trac Macros, Plugins ===== |
| | 110 | 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. |
| | 111 | |
| | 112 | ===== For FCGI/WSGI/CGI users ===== |
| | 113 | For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file: |
| | 114 | {{{ |
| | 115 | trac-admin /path/to/env deploy /deploy/directory/path |
| | 116 | }}} |
| | 117 | |
| | 118 | This will create a deploy directory with the following two subdirectories: `cgi-bin` and `htdocs`. Then update your Apache configuration file `httpd.conf` with this new `trac.cgi` location and `htdocs` location. |
| | 119 | |
| | 120 | ===== Web Admin plugin integrated ===== |
| | 121 | If you had the webadmin plugin installed, you can uninstall it as it is part of the Trac code base since 0.11. |
| | 122 | |
| | 123 | === 7. Restart the Web Server === #RestarttheWebServer |
| | 124 | |
