[Tickets #6814] Re: problem of upgrade turba from 2.1.7 to 2.2

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6814
-----------------------------------------------------------------------
 Ticket             | 6814
 Updated By         | david at tmv.gov.tw
 Summary            | problem of upgrade turba from 2.1.7 to 2.2
 Queue              | Turba
 Version            | 2.2
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             | Michael Rubinsky
-----------------------------------------------------------------------


david at tmv.gov.tw (2008-06-04 17:38) wrote:

> What driver are you using for Shares?  If you switched to the SQL
> driver, did you run the turba upgrade *after* you ran the SQL share
> migration script?
Allways datatree for share.
Because there is error while execute convert_datatree_shares_to_sql.php
,so i stay using datatree as share (see
http://lists.horde.org/archives/turba/Week-of-Mon-20080602/005876.html ).
Here are the scripts i run:
1. horde/scripts/upgrades/3.1_to_3.2.mysql.sql
2. turba/scripts/upgrades/2007-06-17_flatten_shares.php
3. turba/scripts/upgrades/2.1_to_2.2_sql_schema.php
>
> I setup a Horde 3.1/Turba 2.1 install and ran a full conversion with
> fresh data.  The only way I can reproduce this is by switching to the
> SQL share driver and then logging in before I run the sql share
> migration script.  In every other case I tried, the maintenance tasks
> run perfectly.