Changes between Version 5 and Version 6 of TracUpgrade


Ignore:
Timestamp:
May 25, 2020 12:56:14 PM (6 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v5 v6  
    55== Instructions
    66
    7 Typically, there are seven steps involved in upgrading to a newer version of Trac:
    8 
    9 === 1. Bring your server off-line
     7There are seven recommended steps for upgrading to a newer version of Trac:
     8
     9=== 1. Check your plugins
     10
     11Check whether your plugins are compatible with the version of Trac that you are upgrading to. Obsolete plugins listed in the [#VersionSpecificSteps version specific steps] below should be uninstalled or disabled.
     12
     13If you are upgrading to a minor release, plugin compatibility is usually not a concern because the Trac API rarely changes, and major features are usually not introduced, for minor releases.
     14
     15If your plugins are installed from [https://trac-hacks.org trac-hacks.org] you can check compatibility by looking for a tag on the project page corresponding to a major release (e.g. `1.2`). If you are unsure, you'll want to contact the plugin author or ask on the [trac:MailingList MailingList].
     16
     17If you are running several Trac plugins it is good to test the upgrade and plugin functionality in a staging instance of your site before upgrading your production instance. Remember, plugin authors are responsible for Trac version compatibility and plugins can interact in unexpected ways. Your Trac instance may have a unique combination of plugins and therefore it's advised that you do some verification testing when making any changes to your site.
     18
     19=== 2. Bring your server off-line
    1020
    1121It is not a good idea to update a running server: the server processes may have parts of the current packages cached in memory, and updating the code will likely trigger [#ZipImportError internal errors].
    1222
    13 Although a database backup will be implicitly created by default when upgrading the environment, it is always a good idea to perform a full backup of the environment using the [TracBackup hotcopy] command before beginning.
    14 
    15 === 2. Update the Trac Code #UpdatetheTracCode
    16 
    17 Get the new version as described in TracInstall, or through your operating system package manager.
    18 
    19 If you already an earlier version of Trac installed via `easy_install`, it might be easiest to also use `easy_install` to upgrade your Trac installation:
    20 
    21 {{{#!sh
    22 easy_install --upgrade Trac==1.2
    23 }}}
    24 
    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`
    30 
    31 You may also want to remove the directory in which your static resources are [TracInstall#cgi-bin deployed]. The exact location depends on your platform. This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as your installation is uncluttered by code or templates from a previous release that is not used anymore. As usual, make a backup before actually removing things.
    32 
    33 === 3. Upgrade the Trac Environment #UpgradetheTracEnvironment
     23Although a database backup will be implicitly created by default when upgrading the environment, it is always a good idea to perform a full backup of the environment using the [TracBackup hotcopy] command before beginning. You may also wish to create a full backup of your server.
     24
     25=== 3. Update Trac and dependencies #UpdatetheTracCode
     26
     27The packages are available through several channels, as described in [trac:TracDownload]. If your Trac instance was installed through an operating system package manager or an installer on Windows, proceed with the standard steps that are appropriate for your operating system.
     28
     29If you are managing your Trac installation using command line tools, `pip` is the preferred tool to upgrade a Trac instance because it will uninstall the old version. The following command will upgrade your Trac installation using the package published to [https://pypi.python.org/pypi/Trac PyPI].
     30
     31{{{#!sh
     32$ pip install --upgrade Trac
     33}}}
     34
     35The upgrade command will give you the latest release of Trac. If instead you wish to upgrade to a different version, such as a minor release of Trac when there is a newer major release available, then specify the Trac version in the `pip` command.
     36
     37{{{#!sh
     38$ pip install --upgrade Trac==1.2.1
     39}}}
     40
     41You should also upgrade dependencies so they are compliant with the [TracInstall#Dependencies required versions].
     42
     43=== 4. Upgrade the Trac Environment #UpgradetheTracEnvironment
    3444
    3545Environment upgrades are not necessary for minor version releases unless otherwise noted.
    3646
    37 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]:
    38 {{{#!sh
    39 trac-admin /path/to/projenv upgrade
     47On starting your web server after upgrading Trac, a message will be displayed for projects that need to be upgraded and the projects will not be accessible until the upgrade is run.
     48
     49The upgrade is run using a [TracAdmin trac-admin] command:
     50{{{#!sh
     51$ trac-admin /path/to/projenv upgrade
    4052}}}
    4153
    4254This command will not have any effect if the environment is already up-to-date.
    4355
    44 Note that a backup of your database will be performed automatically prior to the upgrade.
    45 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:
    46 {{{#!sh
    47 trac-admin /path/to/projenv upgrade --no-backup
    48 }}}
    49 
    50 === 4. Update the Trac Documentation === #UpdatetheTracDocumentation
    51 
    52 By default, every [TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. However, to keep the included documentation in sync with the installed version of Trac, use the following [TracAdmin trac-admin] command to upgrade the documentation:
    53 {{{#!sh
    54 trac-admin /path/to/projenv wiki upgrade
    55 }}}
    56 
    57 Note that this procedure will leave your `WikiStart` page intact.
    58 
    59 === 5. Refresh static resources
    60 
    61 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:
    62 {{{#!sh
    63 trac-admin /path/to/env deploy /deploy/path
    64 }}}
    65 
    66 This will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
    67 
    68 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.
     56It is recommended that you set the [[TracIni#logging-log_level-option|log_level]] to `INFO` before running the upgrade. The additional information in the logs can be helpful in case something unexpected occurs during the upgrade.
     57
     58Note that a backup of your database will be performed automatically prior to the upgrade. The backup is saved in the location specified by [[TracIni#trac-backup_dir-option|backup_dir]].
     59
     60=== 5. Update the Trac Documentation === #UpdatetheTracDocumentation
     61
     62By default, every [TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. To keep the documentation in sync with the installed version of Trac, upgrade the documentation:
     63{{{#!sh
     64$ trac-admin /path/to/projenv wiki upgrade
     65}}}
     66
     67Note that this procedure will leave your `WikiStart`, `InterMapTxt` and `SandBox` pages unaltered. Local changes to other pages that are distributed with Trac will be overwritten, however these pages are read-only by default for Environments created in Trac 1.3.3 and later.
     68
     69=== 6. Refresh static resources
     70
     71If you have configured your web server to serve static resources directly (accessed using the `/chrome/` URL) then you will need to refresh them using the [TracInstall#MappingStaticResources deploy command]. The `deploy` command will extract static resources and CGI scripts (`trac.wsgi`, etc) from the new Trac version and plugins into `/deploy/path`.
     72{{{#!sh
     73$ trac-admin /path/to/env deploy /deploy/path
     74}}}
     75
     76Before refreshing, it is recommended that you remove the directory in which your static resources are deployed. The directory location depends on the choice you made during installation. This cleanup is not mandatory, but makes it easier to troubleshoot issues as your installation is uncluttered by unused assets from a previous release. As usual, make a backup before deleting the directory.
     77
     78{{{#!div style="border: 1pt dotted; margin: 1em"
     79**Note:** Some web browsers (IE, Opera) cache CSS and !JavaScript files, so you should instruct your users to manually erase the contents of their browser's cache. A forced refreshed (SHIFT + <F5>) should be sufficient.
    6980{{{#!comment
    7081Remove above note once #9936 is fixed.
    7182}}}
    72 
    73 === 6. Steps specific to a given Trac version
     83}}}
     84
     85=== 7. Steps specific to a given Trac version #VersionSpecificSteps
     86
     87==== Upgrading from Trac 1.2 to 1.4 #to1.4
     88
     89===== Python 2.6 no longer supported
     90
     91Upgrade Python to 2.7, but not 3.0 or greater.
     92
     93===== MySQL-python no longer supported
     94
     95[https://pypi.python.org/pypi/PyMySQL PyMySQL] is the supported MySQL database library, support for [https://pypi.python.org/pypi/MySQL-python MySQL-python] has been removed.
     96
     97===== Obsolete Plugins
     98
     99Trac has added functionality equivalent to the following plugins:
     100
     101* [https://trac-hacks.org/wiki/DynamicVariablesPlugin DynamicVariablesPlugin]: dynamic variables are autocompleted
     102* [https://trac-hacks.org/wiki/NavAddPlugin NavAddPlugin]: see TracNavigation
     103* [https://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignToPlugin]: subclass `ConfigurableTicketWorkflow` and override `get_allowed_owners`
     104* [https://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin]: Use the `trac-admin` [TracAdmin#ChangingDatabaseBackend convert_db command]
     105
     106The plugins should be removed when upgrading Trac to 1.4.
     107
     108===== Jinja2 is the new template engine
     109
     110Content is now generated by using the Jinja2 template
     111engine. You may want to verify that your plugins are
     112compatible with this change.
     113(TODO: expand...)
     114
     115If you customized the Trac templates, or the `site.html`
     116template, you'll need to adapt that as well.
     117(TODO: expand...) See [#CustomizedTemplates]
     118
     119===== New permission policies for Wiki and Ticket realms
     120
     121Since 1.3.2 there are new permission policies for the ticket and wiki systems. `DefaultTicketPolicy` allows an authenticated users with `TICKET_APPEND` or `TICKET_CHPROP` to modify the description of a ticket they reported. It also implements the pre-1.3.2 behavior of allowing users to edit their own ticket comments. [#Newpermissionspolicyforread-onlywikipages ReadonlyWikiPolicy], added in 1.1.2, is renamed to `DefaultWikiPolicy`. The new permission policies can be easily replaced with alternate implementations if the default behavior is not desired.
     122
     123If `[trac] permission_policy` has the default value `ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy`, then `DefaultWikiPolicy, DefaultTicketPolicy` should be automatically appended to the list when upgrading the environment:
     124{{{#!ini
     125[trac]
     126permission_policies = DefaultWikiPolicy,
     127 DefaultTicketPolicy,
     128 DefaultPermissionPolicy,
     129 LegacyAttachmentPolicy
     130}}}
     131
     132If other permission policies are enabled, `trac.ini` will need to be edited to add `DefaultWikiPolicy, DefaultTicketPolicy` to `permission_policies`. See [wiki:TracFineGrainedPermissions#DefaultWikiPolicyandDefaultTicketPolicy] for additional details on the proper ordering.
     133
     134===== Description field added to ticket enums #enum-description-field
     135
     136The ticket enums now have a //description// field. An //ambiguous column name// error may be seen for reports that reference the `description` column of another table and join the `enum` table with that table (e.g. `ticket`, `component`). The reports {1}, {2}, {3}, {4}, {5}, {7}, and {8} are modified by an upgrade step to fix the issue, but the modification may not succeed if the default reports have been modified, in which case `upgrade` will output a message to the terminal instructing the user to modify the reports. User-created reports may also need to be modified.
     137
     138Reports that display the error need to be modified to prefix the `description` column with the appropriate table name or alias. For example, if the `ticket` table is aliased as `t` (`ticket t` or `ticket AS t`), replace `description` with `t.description` if the report should use the ticket's `description` column.
     139
     140===== Removed `<repostype>` and `<repospath>` arguments from TracAdmin `initenv` command
     141
     142The TracAdmin `initenv` command allowed the default repository to be specified using the third and fourth positional arguments of `initenv`:
     143{{{
     144initenv [<projectname> <db> [<repostype> <repospath>]]
     145}}}
     146
     147The arguments were an artifact of Trac < 0.12, which only supported a single repository. Trac 0.12 and later supports multiple repositories, which can be specified at the time of environment creation using the `--inherit` and `--config` arguments. See the [TracEnvironment#SourceCodeRepository initenv documentation] for details on specifying source code repositories.
    74148
    75149==== Upgrading from Trac 1.0 to 1.2 #to1.2
     
    83157Trac has added functionality equivalent to the following plugins:
    84158* [https://trac-hacks.org/wiki/AdminEnumListPlugin AdminEnumListPlugin]
     159* [https://trac-hacks.org/wiki/AttachmentNotifyPlugin AttachmentNotifyPlugin]: attachment notifications are sent in Trac 1.0.3 and later
    85160* [https://trac-hacks.org/wiki/DateFieldPlugin DateFieldPlugin]: see the **time** [TracTicketsCustomFields#AvailableFieldTypesandOptions custom field type]
    86 * [https://trac-hacks.org/wiki/GroupBasedRedirectionPlugin GroupBasedRedirectionPlugin]: the default handler can set as a user preference.
     161* [https://trac-hacks.org/wiki/FlexibleReporterNotificationPlugin FlexibleReporterNotificationPlugin]: [trac:CookBook/Notification/Subscriptions custom subscribers] can be implemented in the new extensible notification system
     162* [https://trac-hacks.org/wiki/GroupBasedRedirectionPlugin GroupBasedRedirectionPlugin]: the default handler can set as a user preference
     163* [https://trac-hacks.org/wiki/GroupingAssignToPlugin GroupingAssignToPlugin]: groups and permissions can be used in the [TracWorkflow#BasicTicketWorkflowCustomization set_owner] workflow attribute
    87164* [https://trac-hacks.org/wiki/LinenoMacro LinenoMacro]: see WikiProcessors#AvailableProcessors
    88165* [https://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin NeverNotifyUpdaterPlugin]: see [TracNotification#notification-subscriber-section notification subscribers]
     
    118195Trac has added functionality equivalent to the following plugins:
    119196
     197* [https://trac-hacks.org/wiki/AnchorMacro AnchorMacro]
    120198* [https://trac-hacks.org/wiki/BatchModifyPlugin BatchModifyPlugin]
    121 * [https://trac-hacks.org/wiki/GitPlugin GitPlugin]
     199* [https://trac-hacks.org/wiki/GitPlugin GitPlugin]
    122200* [https://trac-hacks.org/wiki/OverrideEditPlugin OverrideEditPlugin]
     201* [https://trac-hacks.org/wiki/ProgressMeterMacro ProgressMeterMacro]
    123202
    124203The plugins should be removed when upgrading Trac to 1.0.
     
    134213The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled.
    135214
    136 ===== Attachments migrated to new location
    137 
    138 Another 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.
     215===== Attachments migrated to new location #AttachmentsMigrated
     216
     217Another step in the automatic upgrade will change the way the attachments are stored. There have been reports that the attachment migration [#AttachmentsNotMigrated sometimes fails], so it's extra important that you [TracBackup backup your environment].
     218
     219In case the `attachments` directory contains some files which are //not// attachments, the last step of the migration to the new layout will not be completed: 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.
    139220
    140221===== Behavior of `[ticket] default_owner` changed
     
    142223Prior 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.
    143224
    144 ==== Upgrading from Trac 0.11 to Trac 0.12
    145 
    146 ===== Python 2.3 no longer supported
    147 
    148 The minimum supported version of Python is now 2.4.
    149 
    150 ===== SQLite v3.x required
    151 
    152 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.
    153 
    154 ===== [trac:PySqlite] 2 required
    155 
    156 [trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below.
    157 
    158 ===== Obsolete Plugins
    159 
    160 Trac has added functionality equivalent to the following plugins:
    161 
    162 * [https://trac-hacks.org/wiki/AutoQueryPlugin AutoQueryPlugin]
    163 * ​[https://trac-hacks.org/wiki/AdminConsoleProviderPatch AdminConsoleProviderPatch]
    164 * [https://trac-hacks.org/wiki/AnchorMacro AnchorMacro]: see WikiFormatting#SettingAnchors
    165 * [https://trac-hacks.org/wiki/TicketChangePlugin TicketChangePlugin]: see [TracPermissions#TicketSystem TICKET_EDIT_COMMENT permission]
    166 * [https://trac-hacks.org/wiki/TicketDeletePlugin TicketDeletePlugin]: see `tracopt.ticket.deleter`
    167 * [https://trac-hacks.org/wiki/SubversionLocationPlugin SubversionLocationPlugin]: see TracRepositoryAdmin#Repositories
    168 * [https://trac-hacks.org/wiki/WikiCreoleRendererPlugin WikiCreoleRendererPlugin]: see [trac:WikiCreole]
    169 * [https://trac-hacks.org/wiki/RepoRevisionSyntaxPlugin RepoRevisionSyntaxPlugin] (added in 0.12.1)
    170 
    171 The plugins should be removed when upgrading Trac to 0.12.
    172 
    173 ===== Multiple Repository Support
    174 
    175 The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
    176 
    177 This may be of interest to users with only one repository, since there is now a way to avoid the potentially costly resync check at every request.
    178 
    179 ===== Resynchronize the Trac Environment Against the Source Code Repository
    180 
    181 Each [TracEnvironment Trac environment] must be resynchronized against the source code repository in order to avoid errors such as "[trac:#6120 No changeset ??? in the repository]" while browsing the source through the Trac interface:
    182 
    183 {{{#!sh
    184 trac-admin /path/to/projenv repository resync '*'
    185 }}}
    186 
    187 ===== Improved repository synchronization
    188 
    189 In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
    190 
    191 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.
    192 
    193 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 and [TracWorkflow#Howtocombinethetracopt.ticket.commit_updaterwiththetestingworkflow here], 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.
    194 
    195 ===== Authz permission checking
    196 
    197 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.
    198 
    199 ===== Microsecond timestamps
    200 
    201 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.
    202 
    203 ==== Upgrading from Trac 0.10 to Trac 0.11
    204 
    205 ===== Site Templates and Styles
    206 
    207 The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information.
    208 
    209 If you are using custom CSS 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.
    210 
    211 ===== Trac Macros, Plugins
    212 
    213 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.
    214 
    215 ===== For FCGI/WSGI/CGI users
    216 
    217 For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file:
    218 {{{#!sh
    219 trac-admin /path/to/env deploy /deploy/directory/path
    220 }}}
    221 
    222 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.
    223 
    224 ===== Web Admin plugin integrated
    225 
    226 If you had the [trac:WebAdmin] plugin installed, you can uninstall it as it is part of the Trac code base since 0.11.
    227 
    228 ===== New Default Configurable Workflow
    229 
    230 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:
    231 
    232 {{{#!Workflow width=500 height=240
    233 leave = * -> *
    234 leave.operations = leave_status
    235 leave.default = 1
    236 accept = new -> assigned
    237 accept.permissions = TICKET_MODIFY
    238 accept.operations = set_owner_to_self
    239 resolve = new,assigned,reopened -> closed
    240 resolve.permissions = TICKET_MODIFY
    241 resolve.operations = set_resolution
    242 reassign = new,assigned,reopened -> new
    243 reassign.permissions = TICKET_MODIFY
    244 reassign.operations = set_owner
    245 reopen = closed -> reopened
    246 reopen.permissions = TICKET_CREATE
    247 reopen.operations = del_resolution
    248 }}}
    249 
    250 There are some significant caveats in this, such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state. So you will probably want to migrate to "basic" workflow; [trac:source:trunk/contrib/workflow/migrate_original_to_basic.py contrib/workflow/migrate_original_to_basic.py] may be helpful. See TracWorkflow for a detailed description of the new basic workflow.
    251 
    252 === 7. Restart the Web Server #RestarttheWebServer
    253 
    254 If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server.
     225==== Upgrading from older versions of Trac #OlderVersions
     226
     227For upgrades from versions older than Trac 0.12, refer first to [trac:wiki:0.12/TracUpgrade#SpecificVersions TracUpgrade for 0.12].
     228
     229For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions TracUpgrade for 0.10].
    255230
    256231== Known Issues
     
    258233=== Customized Templates
    259234
    260 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 aware 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.
    261 
    262 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 [trac:TracDev/ApiChanges] pages.
     235Trac supports customization of its 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 customize the templates, be aware that you will need to repeat your changes on a copy of the new templates when you upgrade to a new release of Trac (even a minor one), as the templates will evolve. So keep a diff around.
     236
     237The preferred way to perform TracInterfaceCustomization is a custom plugin doing client-side !JavaScript transformation of the generated output, as this is more robust in case of changes: we usually won't modify an element `id` or change its CSS `class`, and if we have to do so, this will be documented in the [trac:TracDev/ApiChanges] pages.
    263238
    264239=== !ZipImportError
    265240
    266 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.
     241Due 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 to anticipate and bring your server down for maintenance before upgrading.
    267242See [trac:#7014] for details.
    268243
     
    271246`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.
    272247
    273 === Trac database upgrade
    274 
    275 A known issue in some versions of [trac: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].
    276 
    277248=== Parent dir
    278249
    279250If you use a Trac parent env configuration and one of the plugins in one child does not work, none of the children will work.
    280251
     252=== Attachments not migrated #AttachmentsNotMigrated
     253
     254There have been reports that attachments are not [#AttachmentsMigrated migrated] when upgrading to Trac 1.0 or later. The cause of the issue has not yet been found. If you encounter this issue, see [https://trac.edgewall.org/wiki/TracFaq#Q:Attachmentsaremissingafterupgrade the FAQ] for a workaround and please report your findings to [trac:#11370].
     255
    281256== Related topics
    282257
    283258=== Upgrading Python
    284259
    285 Upgrading Python to a newer version will require reinstallation of Python packages: Trac itself of course, but also [http://pypi.python.org/pypi/setuptools easy_install], if you've been using that. If you are using Subversion, you'll also need to upgrade the Python bindings for svn.
    286 
    287 ==== Windows and Python 2.6
    288 
    289 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 [trac:TracSubversion]. That package works without tweaking.
    290 
    291 === Changing Database Backend
    292 
    293 The [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.
    294 
    295 === Upgrading from older versions of Trac #OlderVersions
    296 
    297 For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions].
     260Upgrading Python to a newer version will require reinstallation of Python packages: Trac itself of course, but also [TracInstall#Dependencies dependencies]. If you are using Subversion, you'll need to upgrade the [trac:TracSubversion Python bindings for SVN].
     261
     262
    298263
    299264-----