Development

TracUpgrade (diff)

You must first sign up to be able to contribute.

Changes between Version 1 and Version 2 of TracUpgrade

Show
Ignore:
Author:
trac (IP: 127.0.0.1)
Timestamp:
11/24/05 20:19:33 (12 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v1 v2  
    3030}}} 
    3131 
    32 This command will do nothing if the environment is already up-to-date. [[BR]] 
     32This command will do nothing if the environment is already up-to-date. 
     33 
     34Note that if you are using a PostgreSQL database, this command will fail with the message that the environment can only be backed up when you use an SQLite database. This means that you will have to backup the repository and the database manually. Then, to perform the actual upgrade, run: 
     35{{{ 
     36trac-admin /path/to/projenv upgrade --no-backup 
     37}}} 
    3338 
    3439=== Update the Trac Documentation === 
    4348=== Restart the Web Server === 
    4449 
    45 In order to reload the new Trac code you will need to restart your web server (note this is not necessary for plain old CGI, although CGI is discouraged for performance reasons). 
     50In order to reload the new Trac code you will need to restart your web server (note this is not necessary for [wiki:TracCgi CGI]). 
    4651 
    4752== Specific Versions == 
    4954The following sections discuss any extra actions that may need to be taken to upgrade to specific versions of Trac. 
    5055 
     56== From 0.9-beta to 0.9 == 
     57 
     58If inclusion of the static resources (style sheets, javascript, images) is not working, check the value of the `htdocs_location` in trac.ini. For [wiki:TracModPython mod_python], [wiki:TracStandalone Tracd] and [wiki:TracFastCgi FastCGI], you can simply remove the option altogether. For [wiki:TracCgi CGI], you should fix it to point to the URL you mapped the Trac `htdocs` directory to (although you can also remove it and then [wiki:TracCgi#MappingStaticResources map the static resources]). If you're still having problems after removing the option, check the paths in the `trac/siteconfig.py` file and fix them if they're incorrect. 
     59 
     60If you've been using plugins with a beta release of Trac 0.9, or have disabled some of the built-in components, you might have to update the rules for disabling/enabling components in [wiki:TracIni trac.ini]. In particular, globally installed plugins now need to be enabled explicitly. See TracPlugins and TracIni for more information. 
     61 
     62If you want to enable the display of all ticket changes in the timeline (the “Ticket Details” option), you now have to explicitly enable that in [wiki:TracIni trac.ini], too: 
     63 
     64{{{ 
     65[timeline] 
     66ticket_show_details = true 
     67}}} 
     68 
    5169== From 0.8.x to 0.9 == 
    52  
    53 If you're using [wiki:TracCgi CGI] you will want to update your `Alias` to the Trac htdocs static resources.  See the documentation on [wiki:TracCgi#MappingStaticResources mapping static resources] for an example on how to configure this. 
    54  
    55 [wiki:TracFastCgi FastCGI] and [wiki:TracModPython mod_python] users can safely remove any `Alias`es to the Trac htdocs folder since this is no longer used by default. 
    5670 
    5771[wiki:TracModPython mod_python] users will also need to change the name of the mod_python handler in the Apache HTTPD configuration: