[Sommaire] [Imprimer]

   1  =================
   2   Upgrading Horde
   3  =================
   4  
   5  :Last update:   $Date: 2006/06/29 16:29:02 $
   6  :Revision:      $Revision: 1.4.4.11 $
   7  :Contact:       horde@lists.horde.org
   8  
   9  
  10  These are instructions to upgrade from earlier Horde versions. Please backup
  11  your existing data before running any of the steps described below. You can't
  12  use the updated data with your old Horde version anymore.
  13  
  14  After updating to a newer Horde version, or a newer version of **any** Horde
  15  application, you **always** need to update **all** configuration files.
  16  
  17  
  18  Upgrading Horde from 3.1.1 to 3.1.2
  19  ===================================
  20  
  21  
  22  Session Configuration
  23  ---------------------
  24  
  25  A new configuration setting has been added to disable GET-based
  26  sessions.  If this setting is enabled, session IDs will only be stored
  27  in session cookies, requiring the users to enable cookies in their
  28  browser and the cookie settings in Horde's configuration to be correct.
  29  
  30  Using session cookies is much safer since no session information can
  31  be stored in any web server or proxy log files, referrer headers,
  32  browser caches, or browser bookmarks.
  33  
  34  .. Warning:: This setting in enabled by default.
  35  
  36  
  37  Additional Indexes for the Preference Table
  38  -------------------------------------------
  39  
  40  Optionally execute the provided SQL script 2006-06-29_horde_prefs_indexes.sql
  41  to create two additional indexes in the preference table, e.g.::
  42  
  43     mysql --user=root --password=<MySQL-root-password> <db name> < scripts/upgrades/2006-06-29_horde_prefs_indexes.sql
  44  
  45  This increases database performance for some database systems, e.g. PostgreSQL
  46  if you have large preference tables.
  47  
  48  
  49  Upgrading Horde from 3.1 to 3.1.1
  50  =================================
  51  
  52  
  53  MySQL Session Handler
  54  ---------------------
  55  
  56  The mysql session handler has been improved to correctly lock concurrent
  57  accesses to the same session. You need to set in the Horde configuration if
  58  you want to use row-level locking and transactions or table-level
  59  locking. Row-level locking and transactions are only supported by some table
  60  engines like InnoDB, and is recommended for session tables. The default table
  61  type for MySQL is MyISAM though, that only supports table-level locking. If
  62  you used the SQL scripts from Horde 3.1 or earlier to create the session
  63  table, this is probably the current engine of you session table. If you want
  64  to change the table type to InnoDB, execute the following SQL statement::
  65  
  66     ALTER TABLE horde_sessionhandler ENGINE = InnoDB
  67  
  68  
  69  
  70  Upgrading Horde from 3.0.x to 3.1.x
  71  ===================================
  72  
  73  
  74  SQL Backends
  75  ------------
  76  
  77  A few new tables have been added to Horde.
  78  
  79  Execute one of the provided SQL scripts to update your data to the new Horde
  80  version, e.g.::
  81  
  82     mysql --user=root --password=<MySQL-root-password> <db name> < scripts/upgrades/3.0_to_3.1.mysql.sql
  83  
  84  
  85  Groups
  86  ------
  87  
  88  The Horde_Group API uses group IDs instead of group names to avoid ambiguity.
  89  Be sure to update any custom code that uses Horde_Group.
  90  
  91  
  92  History
  93  -------
  94  
  95  The Horde_History storage has been moved out to a separate database table to
  96  drastically improve performance.
  97  
  98  .. Warning:: Migration of the Horde_History data may take a very long time,
  99               possibly days, depending on the number of entries.  Be sure to
 100               execute this script from a location where it will not be timed
 101               out by firewall or terminal timeouts.
 102  
 103  Execute the provided PHP script to migrate your histories to the new table::
 104  
 105     php scripts/upgrades/move_history_out_of_datatree.php
 106  
 107  
 108  
 109  Upgrading Horde from 2.x to 3.0.x
 110  =================================
 111  
 112  
 113  Configuration files
 114  -------------------
 115  
 116  The configuration files have been changed to XML format.  To generate a valid
 117  configuration file from the XML file, follow the configuration instructions
 118  in the applications' ``docs/INSTALL`` file.
 119  
 120  
 121  Preferences
 122  -----------
 123  
 124  The ``last_login`` and ``date_format`` preferences have changed their format
 125  and/or scope.  Just remove all ``last_login`` and ``date_format`` preferences
 126  from the preferences backend.
 127  
 128  
 129  SQL Backends
 130  ------------
 131  
 132  A few new tables have been added to Horde.
 133  
 134  Execute the provided SQL script to update your data to the new Horde version::
 135  
 136     mysql --user=root --password=<MySQL-root-password> <db name> < scripts/upgrades/2.2_to_3.0.mysql.sql