Execute the provided PHP script to migrate your histories to the new table::
php scripts/upgrades/move_history_out_of_datatree.php
-
-
-Upgrading Horde from 2.x to 3.0.x
-=================================
-
-
-Configuration files
--------------------
-
-The configuration files have been changed to XML format. To generate a valid
-configuration file from the XML file, follow the configuration instructions
-in the applications' ``docs/INSTALL`` file.
-
-
-Preferences
------------
-
-The ``last_login`` and ``date_format`` preferences have changed their format
-and/or scope. Just remove all ``last_login`` and ``date_format`` preferences
-from the preferences backend.
-
-
-SQL Backends
-------------
-
-A few new tables have been added to Horde.
-
-Execute the provided SQL script to update your data to the new Horde version::
-
- mysql --user=root --password=<MySQL-root-password> <db name> < scripts/upgrades/2.2_to_3.0.mysql.sql
The format for saved Virtual Folders has changed. To convert to the new
format you must run the script located at
``scripts/upgrades/convert_vfolders.php``.
-
-
-Upgrading IMP From 3.x To 4.0.x
-===============================
-
-This is a non-exhaustive, quick explanation of what has changed between an IMP
-3.x installation to IMP 4.0.x.
-
-
-Filters
--------
-
-Filtering code has been removed from IMP. To have the same features as the
-old code, you should install the Ingo_ module. See the INSTALL_ file for more
-information.
-
-.. _Ingo: http://www.horde.org/ingo/
-.. _INSTALL: ?f=INSTALL.html
-.. _FCKeditor: http://www.fckeditor.net/
used to be called "search_abook" and contained a serialized PHP array. The new
preference is called "search_sources", contains a tab-separated list, and goes
along with the "search_fields" preference.
-
-
-Upgrading Kronolith from 1.1.x to 2.0.x
-=======================================
-
-
-SQL Backends
-------------
-
-Three new fields and a new table have been added to the default SQL table
-layout to provide the scheduling features to Kronolith.
-
-Execute the provided SQL script to update your data to the new Kronolith
-version::
-
- mysql --user=root --password=<MySQL-root-password> <db name> < scripts/upgrades/1.1_to_2.0.mysql.sql
-
-
-Categories
-----------
-
-Categories are now being maintained centrally for all Horde applications that
-support them. To convert the old event categories execute the provided PHP
-script::
-
- php scripts/upgrades/2004-05-19_convert_categories_to_strings.php
provided PHP script to migrate your existing share data to the new format::
php scripts/upgrades/convert_datatree_shares_to_sql.php
-
-
-Upgrading Mnemo from 1.1.x to 2.0
-=================================
-
-
-SQL Backends
-============
-
-Execute the provided SQL script to update your data to the new Mnemo version::
-
- mysql --user=root --password=<MySQL-root-password> <db name> < scripts/upgrades/1.1_to_2.0.mysql.sql
-
-
-Categories
-==========
-
-Categories are now being maintained centrally for all Horde applications that
-support them. To convert the old memo categories execute the provided PHP
-script::
-
- php scripts/upgrades/2004-05-19_convert_categories_to_strings.php
provided PHP script to migrate your existing share data to the new format::
php scripts/upgrades/convert_datatree_shares_to_sql.php
-
-
-Upgrading Nag from 1.1.x to 2.0.x
-=================================
-
-
-SQL Backends
-------------
-
-Two new fields have been added to the default SQL table layout. The new
-``task_uid`` field provides a global unique ID to task items, the
-``task_alarm`` allows you to set alarm notification on due dates.
-
-Execute the provided SQL script to update your data to the new Nag version::
-
- mysql --user=root --password=<MySQL-root-password> <db name> < scripts/upgrades/1.1_to_2.0.mysql.sql
-
-
-Categories
-----------
-
-Categories are now being maintained centrally for all Horde applications that
-support them. To convert the old task categories execute the provided PHP
-script::
-
- php scripts/upgrades/2004-05-13_convert_categories_to_strings.php
need for maintaining the two seperate tables. If you desire not
to enable share support, you may still use seperate tables and
set permissions via the administration interface.
-
-
-Upgrading to Turba 2.0
-======================
-
-These are instructions to upgrade from Turba 1.2.x to Turba 2.0. Please
-backup your existing data before running any of the steps described below.
-You can't use the updated data with your old Turba version anymore.
-
-.. Important:: These upgrade instructions assume that you are upgrading from
- at least Turba 1.2. If you have an older version of Turba,
- follow the upgrade steps described in `Upgrading to Turba 1.2`_
- first.
-
-
-SQL Backends
-------------
-
-Four new fields have been added to the default SQL table layout, one being
-mandatory. The new ``object_uid`` field provides a global unique ID to
-objects.
-
-Execute the provided SQL script to update your data to the new Turba version::
-
- mysql --user=root --password=<MySQL-root-password> <db name> < 1.2_to_2.0.sql
- psql <db name> -f 1.2_to_2.0.sql
-
-
-History
--------
-
-The contacts history is now being maintained by the global Horde History
-backend. To create default history entries execute the provided PHP script::
-
- php scripts/upgrades/create_default_histories.php
-
-
-Upgrading to Turba 1.2
-======================
-
-These are instructions to upgrade from Turba 1.1 to Turba 1.2. Please backup
-your existing data before running any of the steps described below. You will
-no longer be able to use your data with older versions of Turba.
-
-
-SQL Backends
-------------
-
-The SQL schema for the SQL address book has changed. Please update your SQL
-table to the new schema after you update to Turba 1.2. The fields
-``object_type`` and ``object_members`` have been added (needed for
-distribution lists) and the fields ``object_homeaddress``,
-``object_workaddress``, ``object_homephone``, ``object_workphone`` and
-``object_cellphone`` have changed to all lowercase.
-
-If you are using a MySQL or PostgreSQL database you can also use the update
-script available in ``scripts/upgrades/1.1_to_1.2.sql``.
-
-
-LDAP Backends
--------------
-
-The LDAP schema for the shared LDAP address book has changed. Please update
-your LDAP directory to use the new schema after you update to Turba 1.2, and
-also update ``config/sources.php`` accordingly.
-
-The ``objectclass`` entry for LDAP address book definitions in
-``config/sources.php`` is respected in Turba 1.2 but wasn't before, so you
-should make sure that you use a correct setting here.
-
-
-IMP Integration
----------------
-
-If you were using IMP_ 3.1 you should also upgrade to IMP 3.2; distribution
-list support in Turba 1.2/IMP 3.2 is not compatible with how the contacts
-window in IMP 3.1 worked. However, IMP 3.0 did not have this window, and will
-probably play nicely with Turba 1.2.
-
-.. _IMP: http://www.horde.org/imp/
projects / horde.git / commitdiff