Edgewall Software

Changes between Version 21 and Version 22 of 1.1/TracUpgrade


Ignore:
Timestamp:
Jun 22, 2016, 10:57:16 AM (5 years ago)
Author:
figaro
Comment:

Cosmetic changes (refs TracUpgrade@119)

Legend:

Unmodified
Added
Removed
Modified
  • 1.1/TracUpgrade

    v21 v22  
    4141}}}
    4242
    43 This command will do nothing if the environment is already up-to-date.
     43This command will not have any effect if the environment is already up-to-date.
    4444
    4545Note that a backup of your database will be performed automatically prior to the upgrade.
    46 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:
     46This 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:
    4747{{{#!sh
    4848trac-admin /path/to/projenv upgrade --no-backup
     
    6464trac-admin /path/to/env deploy /deploy/path
    6565}}}
    66 this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
     66
     67This will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
    6768
    6869Some 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.
     
    7677
    7778===== Python 2.5 no longer supported
     79
    7880Upgrade Python to at least 2.6 or 2.7, but not 3.0 or greater.
    7981
    8082===== Obsolete Plugins
     83
    8184Trac has added functionality equivalent to the following plugins:
    8285* [https://trac-hacks.org/wiki/AdminEnumListPlugin AdminEnumListPlugin]
     
    9295===== New workflow actions #NewWorkflowActions
    9396
    94 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.
     97The ticket creation step is 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.
    9598
    9699===== New permissions policy for read-only wiki pages
     100
    97101Since 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:
    98102{{{#!ini
     
    102106 LegacyAttachmentPolicy
    103107}}}
    104 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.
     108
     109If other permission policies are enabled, `trac.ini` will need to have `ReadonlyWikiPolicy` appended to the list of active `permission_policies`. See TracFineGrainedPermissions#ReadonlyWikiPolicy for additional details on the proper ordering.
    105110
    106111==== Upgrading from Trac 0.12 to Trac 1.0 #to1.0
    107112
    108113===== Python 2.4 no longer supported
     114
    109115Upgrade Python to at least 2.5, but not 3.0.
    110116
     
    120126
    121127===== Subversion components not enabled by default for new installations
     128
    122129The Trac components for Subversion support are no longer enabled by default. To enable the svn support, you need to make sure the `tracopt.versioncontrol.svn` components are enabled, for example by setting the following in the TracIni:
    123130{{{#!ini
     
    125132tracopt.versioncontrol.svn.* = enabled
    126133}}}
     134
    127135The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled.
    128136
    129137===== Attachments migrated to new location
     138
    130139Another 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.
    131140
    132141===== Behavior of `[ticket] default_owner` changed
     142
    133143Prior 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.
    134144
     
    136146
    137147===== Python 2.3 no longer supported
     148
    138149The minimum supported version of Python is now 2.4.
    139150
    140151===== SQLite v3.x required
     152
    141153SQLite 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.
    142154
    143155===== [trac:PySqlite] 2 required
     156
    144157[trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below.
    145158
     
    160173
    161174===== Multiple Repository Support
     175
    162176The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
    163177
     
    173187
    174188===== Improved repository synchronization
     189
    175190In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
    176191
     
    180195
    181196===== Authz permission checking
     197
    182198The 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.
    183199
    184200===== Microsecond timestamps
     201
    185202All 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.
    186203
    187204==== Upgrading from Trac 0.10 to Trac 0.11
     205
    188206===== Site Templates and Styles
     207
    189208The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information.
    190209
     
    192211
    193212===== Trac Macros, Plugins
     213
    194214The 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.
    195215
    196216===== For FCGI/WSGI/CGI users
     217
    197218For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file:
    198219{{{#!sh
     
    203224
    204225===== Web Admin plugin integrated
     226
    205227If you had the [trac:WebAdmin] plugin installed, you can uninstall it as it is part of the Trac code base since 0.11.
    206228
    207229===== New Default Configurable Workflow
    208230
    209 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.
    210 
    211 Graphically, that looks like this:
     231When 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:
    212232
    213233{{{#!Workflow width=500 height=240
     
    249269
    250270=== Wiki Upgrade
     271
    251272`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.
    252273
     
    256277
    257278=== Parent dir
     279
    258280If you use a Trac parent env configuration and one of the plugins in one child does not work, none of the children will work.
    259281
     
    270292=== Changing Database Backend
    271293
    272 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.
     294The [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.
    273295
    274296=== Upgrading from older versions of Trac #OlderVersions