| 27 | | Unless noted otherwise, upgrading between major versions (such as 0.8 and 0.9) involves changes to the database schema, and possibly the layout of the [wiki:TracEnvironment environment directory]. Fortunately, Trac provides automated upgrade scripts to ease the pain. These scripts are run via [wiki:TracAdmin trac-admin]: |
| | 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 |
| | 31 | |
| | 32 | Environment upgrades are not necessary for minor version releases unless otherwise noted. |
| | 33 | |
| | 34 | After restarting, Trac should show the instances which need a manual upgrade via the automated upgrade scripts to ease the pain. These scripts are run via [TracAdmin trac-admin]: |
| 50 | | In order to reload the new Trac code you will need to restart your web server (note this is not necessary for [wiki:TracCgi CGI]). |
| 51 | | |
| 52 | | == Specific Versions == |
| 53 | | |
| 54 | | The following sections discuss any extra actions that may need to be taken to upgrade to specific versions of Trac. |
| 55 | | |
| 56 | | == From 0.9.x to 0.10.x == |
| 57 | | |
| 58 | | Due to some changes in the Wiki syntax, you may notice that certain parts of your pages no longer work as expected: |
| 59 | | * Previously, links to images would result in that image being embedded into the page. Since 0.10, links to images remain plain links. If you want to embed an image in the page, use the `[[Image]]` macro. |
| 60 | | * You can no longer use `%20` in wiki links to encode spaces. Instead, you should quote the name containing spaces (for example, use `wiki:"My page"` instead of `wiki:My%20page`.) |
| 61 | | |
| 62 | | Several enhancements have been made to the version control subsystem, in particular for the support of scoped repositories has been improved. |
| 63 | | It is recommended that you perform a [TracAdmin#InteractiveMode trac-admin] '''`resync`''' operation to take advantage of these improvements. |
| 64 | | |
| 65 | | Also note that the argument list of the [TracAdmin trac-admin] '''`initenv`''' command has changed: there's a new argument for determining the type of version control system. The old usage was: |
| 66 | | {{{ |
| 67 | | initenv <projectname> <db> <repospath> <templatepath> |
| 68 | | }}} |
| 69 | | The new usage is: |
| 70 | | {{{ |
| 71 | | initenv <projectname> <db> <repostype> <repospath> <templatepath> |
| 72 | | }}} |
| 73 | | If you're using any scripts that automate the creation of Trac environments, you will need to update them. If you're using Subversion, specify `svn` for the `<repostype>` argument. |
| 74 | | |
| 75 | | == From 0.9.3 to 0.9.4 == |
| 76 | | |
| 77 | | There is a bug in Pysqlite 1.x that causes reports using the "%" character for `LIKE` clauses or date formatting to fail. You will need to use escape the percent characters with another: "%%". |
| 78 | | |
| 79 | | == From 0.9.x to 0.9.3 or later == |
| 80 | | |
| 81 | | If you are using plugins you might need to upgrade them. See http://projects.edgewall.com/trac/milestone/0.9.3 for further details. |
| 82 | | |
| 83 | | == From 0.9-beta to 0.9 == |
| 84 | | |
| 85 | | If inclusion of the static resources (style sheets, javascript, images) is not working, check the value of the `htdocs_location` in trac.ini. For [wiki:TracModPython mod_python], [wiki:TracStandalone Tracd] and [wiki:TracFastCgi FastCGI], you can simply remove the option altogether. For [wiki:TracCgi CGI], you should fix it to point to the URL you mapped the Trac `htdocs` directory to (although you can also remove it and then [wiki:TracCgi#MappingStaticResources map the static resources]). If you're still having problems after removing the option, check the paths in the `trac/siteconfig.py` file and fix them if they're incorrect. |
| 86 | | |
| 87 | | If you've been using plugins with a beta release of Trac 0.9, or have disabled some of the built-in components, you might have to update the rules for disabling/enabling components in [wiki:TracIni trac.ini]. In particular, globally installed plugins now need to be enabled explicitly. See TracPlugins and TracIni for more information. |
| 88 | | |
| 89 | | If you want to enable the display of all ticket changes in the timeline (the “Ticket Details” option), you now have to explicitly enable that in [wiki:TracIni trac.ini], too: |
| | 58 | 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: |
| 100 | | from: PythonHandler trac.ModPythonHandler |
| 101 | | to: PythonHandler trac.web.modpython_frontend |
| | 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 | ==== Upgrading from Trac 0.10 to Trac 0.11 ==== |
| | 101 | ===== Site Templates and Styles ===== |
| | 102 | The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information. |
| | 103 | |
| | 104 | 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. |
| | 105 | |
| | 106 | ===== Trac Macros, Plugins ===== |
| | 107 | 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. |
| | 108 | |
| | 109 | ===== For FCGI/WSGI/CGI users ===== |
| | 110 | For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file: |
| | 111 | {{{ |
| | 112 | trac-admin /path/to/env deploy /deploy/directory/path |
| 123 | | 0.8 adds a new roadmap feature which requires additional permissions. While a |
| 124 | | fresh installation will by default grant ROADMAP_VIEW and MILESTONE_VIEW |
| 125 | | permissions to anonymous, these permissions have to be granted manually when |
| 126 | | upgrading: |
| 127 | | {{{ |
| 128 | | $ trac-admin /path/to/projectenv permission add anonymous MILESTONE_VIEW |
| 129 | | $ trac-admin /path/to/projectenv permission add anonymous ROADMAP_VIEW |
| 130 | | }}} |
| | 129 | === Wiki Upgrade === |
| | 130 | `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. |
| | 131 | |
| | 132 | === Trac database upgrade === |
| | 133 | |
| | 134 | 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]. |
| | 135 | |
| | 136 | == Upgrading Python == |
| | 137 | |
| | 138 | 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. |
| | 139 | |
| | 140 | === Windows and Python 2.6 === |
| | 141 | |
| | 142 | If you've been using !CollabNet's Subversion package, you may need to uninstall that in favor of [http://alagazam.net/ Algazam], which has the Python bindings readily available (see TracSubversion). The good news is, that works with no tweaking. |
| | 143 | |
| | 144 | == Changing Database Backend == |
| | 145 | === SQLite to PostgreSQL === |
| | 146 | |
| | 147 | 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 |
| | 148 | |
| | 149 | == Older Versions == |
| | 150 | |
| | 151 | For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions]. |
