[horde] Documentation on Horde/composer

[Ralf Lang]

Hi Brent,


> I am having a few issues trying to get php 8.1 running with the 
> basics: horde, imp, kronolith, and turba.
>
> I'm using the dev_framework6 stuff on a Fedora 36 at the moment.
>
> I got horde up and running. I can also now login and authenticate with 
> IMP (yay!). I have a few issues with the configuration or database, 
> however.
>
> #1: Upon login, a pop-up in the corner says: At least one database 
> schema is outdated. When I go to Administration -> Configuration, I 
> see that Horde_Kronolith and Horde_Turba show "SQL DB schema is out of 
> date." If I click on either of those, I get an error that says 
> "SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 
> 'share_parents'"
> If I try to run the "vendor/bin/horde-db-migrate" script, I get this 
> error near the bottom:
>
> Migrating to KronolithUpgradeSqlhierarchical (16)
> == 16 KronolithUpgradeSqlhierarchical: migrating 
> ==============================
> -- addColumn('kronolith_shares', 'share_parents', 'text')
> SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 
> 'share_parents'
> [  INFO  ] Current Horde_Turba schema version: 3
> Migrating to TurbaUpgradeSqlhierarchical (4)
> == 4 TurbaUpgradeSqlhierarchical: migrating 
> ===================================
> -- addColumn('turba_shares', 'share_parents', 'text')
> SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 
> 'share_parents'
>
I see where this comes from. The migrator tries to apply the migrations 
twice.
I just provided a new patch of horde/core which should fix this.


Try

composer update horde/core
./vendor/bin/horde-db-migrate

That should fix it.