Changes between Version 15 and Version 16 of TracUpgrade


Ignore:
Timestamp:
14/06/2017 12:47:23 (7 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v15 v16  
    2020
    2121{{{#!sh
    22 easy_install --upgrade Trac==1.2
     22easy_install --upgrade Trac
    2323}}}
    2424
     
    4242This command will not have any effect if the environment is already up-to-date.
    4343
    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 }}}
     44Note 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`.
    4945
    5046=== 4. Update the Trac Documentation === #UpdatetheTracDocumentation
     
    5955=== 5. Refresh static resources
    6056
    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:
     57If 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]:
    6258{{{#!sh
    6359trac-admin /path/to/env deploy /deploy/path
    6460}}}
    6561
    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.
     62This 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.
    6966{{{#!comment
    7067Remove above note once #9936 is fixed.
     68}}}
    7169}}}
    7270
     
    9492===== New workflow actions #NewWorkflowActions
    9593
    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.
     94The 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.
    9795
    9896===== New permissions policy for read-only wiki pages