ingo::upgrade::problem

[Rafael Berez]

Hello list,

we are upgrading ingo from v. 1.1 to 1.2.1.
we want to use the new SQL table as a storage backend for our filter rules.
we encountered the following problem:

after running the provided PHP script "convert_prefs_to_sql.php", the already existing filter rules remain in the
horde_prefs table but newly created filter rules are written to the corresponding tables (e.g. ingo_forwards).

Sould already existing filter rules not be migrated to the new tables too??


thank's Rafael



_________________________________________________________________
Show them the way! Add maps and directions to your party invites.
http://www.microsoft.com/windows/windowslive/products/events.aspx
--
Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: ingo-unsubscribe@...

[Jan Schneider]

Zitat von Rafael Berez <idcommunication@...>:

>
> Hello list,
>
> we are upgrading ingo from v. 1.1 to 1.2.1.
> we want to use the new SQL table as a storage backend for our filter rules.
> we encountered the following problem:
>
> after running the provided PHP script "convert_prefs_to_sql.php",  
> the already existing filter rules remain in the
> horde_prefs table but newly created filter rules are written to the  
> corresponding tables (e.g. ingo_forwards).
>
> Sould already existing filter rules not be migrated to the new tables too??

Yes, that's the purpose of that script. What's the output of the script?

Jan.

--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/


--
Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: ingo-unsubscribe@...