Changes between Version 6 and Version 7 of Trac Upgrade


Ignore:
Timestamp:
2016-09-26T19:56:31+01:00 (3 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Trac Upgrade

    v6 v7  
    4242}}}
    4343
    44 This command will do nothing if the environment is already up-to-date.
     44This command will not have any effect if the environment is already up-to-date.
    4545
    4646Note that a backup of your database will be performed automatically prior to the upgrade.
    47 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:
     47This 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:
    4848{{{#!sh
    4949trac-admin /path/to/projenv upgrade --no-backup
     
    6565trac-admin /path/to/env deploy /deploy/path
    6666}}}
     67
    6768this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
    6869
     
    7778
    7879===== Python 2.4 no longer supported
     80
    7981Upgrade Python to at least 2.5, but not 3.0.
    8082
     
    106108
    107109===== Python 2.3 no longer supported
     110
    108111The minimum supported version of Python is now 2.4.
    109112
    110113===== SQLite v3.x required
     114
    111115SQLite 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.
    112116
    113117===== [trac:PySqlite] 2 required
     118
    114119[trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below.
    115120
     
    130135
    131136===== Multiple Repository Support
     137
    132138The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
    133139
     
    143149
    144150===== Improved repository synchronization
     151
    145152In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
    146153
     
    150157
    151158===== Authz permission checking
     159
    152160The 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.
    153161
    154162===== Microsecond timestamps
     163
    155164All 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.
    156165
    157166==== Upgrading from Trac 0.10 to Trac 0.11
     167
    158168===== Site Templates and Styles
     169
    159170The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information.
    160171
     
    162173
    163174===== Trac Macros, Plugins
     175
    164176The 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.
    165177
    166178===== For FCGI/WSGI/CGI users
     179
    167180For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file:
    168181{{{#!sh
     
    177190===== New Default Configurable Workflow
    178191
    179 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.
    180 
    181 Graphically, that looks like this:
     192When 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:
    182193
    183194{{{#!Workflow width=500 height=240
     
    243254=== Changing Database Backend
    244255
    245 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.
     256The [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.
    246257
    247258=== Upgrading from older versions of Trac #OlderVersions