close
Warning:
Can't synchronize with repository "(default)" (/common/SVN/wimax does not appear to be a Subversion repository.). Look in the Trac log for more information.
- Timestamp:
-
Jan 30, 2019, 11:46:28 PM (5 years ago)
- Author:
-
trac
- Comment:
-
—
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v3
|
v4
|
|
20 | 20 | |
21 | 21 | {{{#!sh |
22 | | easy_install --upgrade Trac |
| 22 | easy_install --upgrade Trac==1.2 |
23 | 23 | }}} |
24 | 24 | |
… |
… |
|
42 | 42 | This command will not have any effect if the environment is already up-to-date. |
43 | 43 | |
44 | | Note that a backup of your database will be performed automatically prior to the upgrade. The backup will be saved in the location specified by `[trac]` `backup_dir`. |
| 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 | }}} |
45 | 49 | |
46 | 50 | === 4. Update the Trac Documentation === #UpdatetheTracDocumentation |
… |
… |
|
55 | 59 | === 5. Refresh static resources |
56 | 60 | |
57 | | If 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 same command]: |
| 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: |
58 | 62 | {{{#!sh |
59 | 63 | trac-admin /path/to/env deploy /deploy/path |
60 | 64 | }}} |
61 | 65 | |
62 | | This will extract static resources and CGI scripts (`trac.wsgi`, etc) from the new Trac version and plugins into `/deploy/path`. |
63 | | |
64 | | {{{#!div style="border: 1pt dotted; margin: 1em" |
65 | | **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 enough. |
| 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. |
66 | 69 | {{{#!comment |
67 | 70 | Remove above note once #9936 is fixed. |
68 | | }}} |
69 | 71 | }}} |
70 | 72 | |
… |
… |
|
92 | 94 | ===== New workflow actions #NewWorkflowActions |
93 | 95 | |
94 | | The ticket creation step is controlled with a [TracWorkflow#TicketCreateAction 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. |
| 96 | The 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. |
95 | 97 | |
96 | 98 | ===== New permissions policy for read-only wiki pages |
… |
… |
|
117 | 119 | |
118 | 120 | * [https://trac-hacks.org/wiki/BatchModifyPlugin BatchModifyPlugin] |
119 | | * [https://trac-hacks.org/wiki/GitPlugin GitPlugin] |
| 121 | * [https://trac-hacks.org/wiki/GitPlugin GitPlugin] |
120 | 122 | * [https://trac-hacks.org/wiki/OverrideEditPlugin OverrideEditPlugin] |
121 | 123 | |
… |
… |
|
159 | 161 | |
160 | 162 | * [https://trac-hacks.org/wiki/AutoQueryPlugin AutoQueryPlugin] |
161 | | * [https://trac-hacks.org/wiki/AdminConsoleProviderPatch AdminConsoleProviderPatch] |
| 163 | * [https://trac-hacks.org/wiki/AdminConsoleProviderPatch AdminConsoleProviderPatch] |
162 | 164 | * [https://trac-hacks.org/wiki/AnchorMacro AnchorMacro]: see WikiFormatting#SettingAnchors |
163 | 165 | * [https://trac-hacks.org/wiki/TicketChangePlugin TicketChangePlugin]: see [TracPermissions#TicketSystem TICKET_EDIT_COMMENT permission] |
… |
… |
|
246 | 248 | }}} |
247 | 249 | |
248 | | 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:branches/1.2-stable/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. |
| 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. |
249 | 251 | |
250 | 252 | === 7. Restart the Web Server #RestarttheWebServer |
… |
… |
|
258 | 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. |
259 | 261 | |
260 | | 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 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. |
| 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. |
261 | 263 | |
262 | 264 | === !ZipImportError |