| 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 .eggs 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 common: |
| 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 | 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. |
| | 26 | 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: |
| | 27 | * on Linux: `/usr/lib/python2.X/site-packages` |
| | 28 | * on Windows: `C:\Python2.X\lib\site-packages` |
| | 29 | * on MacOSX: `/Library/Python/2.X/site-packages` |
| 60 | | === 4. Resynchronize the Trac Environment Against the Source Code Repository === |
| | 61 | |
| | 62 | === 5. Refresh static resources === |
| | 63 | |
| | 64 | 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: |
| | 65 | {{{ |
| | 66 | trac-admin /path/to/env deploy /deploy/path |
| | 67 | }}} |
| | 68 | this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. |
| | 69 | |
| | 70 | 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. |
| | 71 | {{{#!comment |
| | 72 | Remove above note once #9936 is fixed. |
| | 73 | }}} |
| | 74 | |
| | 75 | === 6. Steps specific to a given Trac version === |
| | 76 | ==== Upgrading from Trac 0.11 to Trac 0.12 ==== |
| | 77 | |
| | 78 | ===== Python 2.3 no longer supported ===== |
| | 79 | The minimum supported version of python is now 2.4 |
| | 80 | |
| | 81 | ===== SQLite v3.x required ===== |
| | 82 | 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. |
| | 83 | |
| | 84 | ===== PySqlite 2 required ===== |
| | 85 | PySqlite 1.1.x is no longer supported. Please install 2.5.5 or later if possible (see [#Tracdatabaseupgrade Trac database upgrade] below). |
| | 86 | |
| | 87 | ===== Multiple Repository Support ===== |
| | 88 | The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration. |
| | 89 | |
| | 90 | 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. |
| | 91 | |
| | 92 | ===== Resynchronize the Trac Environment Against the Source Code Repository ===== |
| 68 | | === 5. Steps specific to a given Trac version === |
| 69 | | ==== Upgrading to Trac 0.11 ==== |
| 70 | | ===== Site Templates ===== |
| 71 | | The templating engine has changed in 0.11, please look at TracInterfaceCustomization for more information. |
| | 100 | ===== Improved repository synchronization ===== |
| | 101 | In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories. |
| | 102 | |
| | 103 | 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. |
| | 104 | |
| | 105 | 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. |
| | 106 | |
| | 107 | ===== Authz permission checking ===== |
| | 108 | 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). |
| | 109 | |
| | 110 | ===== Microsecond timestamps ===== |
| | 111 | 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. |
| | 112 | |
| | 113 | ==== Upgrading from Trac 0.10 to Trac 0.11 ==== |
| | 114 | ===== Site Templates and Styles ===== |
| | 115 | The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information. |
| | 116 | |
| | 117 | 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. |
| 93 | | === some core modules won't load === |
| 94 | | This can happen in particular with Python 2.3 on Windows when upgrading without uninstalling first. |
| 95 | | Some modules were previously capitalized and were changed to lower case, e.g. trac/About.py became trac/about.py. You may find such messages in the Trac log: |
| 96 | | {{{ |
| 97 | | ERROR: Skipping "trac.about = trac.about": (can't import "No module named about") |
| 98 | | }}} |
| 99 | | Remove the `Lib/site-packages/trac` folder and reinstall. |
| | 141 | === Customized Templates |
| | 142 | |
| | 143 | 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 ;-) |
| | 144 | |
| | 145 | 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. |
| | 146 | |
| | 147 | === !ZipImportError === |
| | 148 | |
| | 149 | 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. |
| | 150 | See [trac:#7014] for details. |
| 105 | | == Changing Database Backend == |
| 106 | | === SQLite to PostgreSQL === |
| | 157 | 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]. |
| | 158 | |
| | 159 | === parent dir === |
| | 160 | If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work. |
| | 161 | |
| | 162 | == Related topics |
| | 163 | |
| | 164 | === Upgrading Python === |
| | 165 | |
| | 166 | 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. |
| | 167 | |
| | 168 | ==== Windows and Python 2.6 ==== |
| | 169 | |
| | 170 | 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. |
| | 171 | |
| | 172 | === Changing Database Backend === |
| | 173 | ==== SQLite to PostgreSQL ==== |
