• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Problem of address book in Horde

There doesn't seem to be anything Plesk specific in the Turba package with the code other then there seems to be missing files so I did a straight swap of the package from Horde http://www.horde.org/download/app/?app=turba and symlinked the 'config' directory to '/etc/psa-webmail/horde/turba/' and all the links appear to be working now for Turba.
 
Developers are working on it and I have requested workaround. I will post it when it will be ready.
 
I am looking for this fix Also please update

I am looking for this fix Also please update once a fix is available.
 
Workaround

It is possible to restore the old psa-turba package (Debian: /var/cache/apt/archives), for example (Debian):

dpkg- i psa-turba_2.1.7-debian5.0.build93091230.07_i386.deb

So, the address book will work immediately.
 
I reinstall everything and the addressbook shows up, but is not allowing me to add contacts.

"There was an error adding the new contact. Contact your system administrator for further help."

no error shows up on any log.

besides all the contacts are despaired.
 
this fix solved my problem...

The update from turba 2.1 to 2.3 doesn't alter the tables on the database turba_objects

I try to run the patch 2.1_to_2.2_sql_schema.php
but it gave a lot of errors becasue it didnt found the PEAR.php object. I tried to update all the paths but always find another error so I get tired, and I just copy the SQL code and I run it straight away into the database.


ALTER TABLE turba_objects ADD COLUMN object_firstname VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_lastname VARCHAR(255);
UPDATE turba_objects SET object_lastname = object_name;
ALTER TABLE turba_objects DROP COLUMN object_name;
ALTER TABLE turba_objects ADD COLUMN object_middlenames VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_nameprefix VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_namesuffix VARCHAR(32);
ALTER TABLE turba_objects ADD COLUMN object_phototype VARCHAR(10);
ALTER TABLE turba_objects ADD COLUMN object_bday VARCHAR(10);
ALTER TABLE turba_objects ADD COLUMN object_homestreet VARCHAR(255);
UPDATE turba_objects SET object_homestreet = object_homeaddress;
ALTER TABLE turba_objects DROP COLUMN object_homeaddress;
ALTER TABLE turba_objects ADD COLUMN object_homepob VARCHAR(10);
ALTER TABLE turba_objects ADD COLUMN object_homecity VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_homeprovince VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_homepostalcode VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_homecountry VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_workstreet VARCHAR(255);
UPDATE turba_objects SET object_workstreet = object_workaddress;
ALTER TABLE turba_objects DROP COLUMN object_workaddress;
ALTER TABLE turba_objects ADD COLUMN object_workpob VARCHAR(10);
ALTER TABLE turba_objects ADD COLUMN object_workcity VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_workprovince VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_workpostalcode VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_workcountry VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_tz VARCHAR(32);
ALTER TABLE turba_objects ADD COLUMN object_geo VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_pager VARCHAR(25);
ALTER TABLE turba_objects ADD COLUMN object_role VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_logotype VARCHAR(10);
ALTER TABLE turba_objects ADD COLUMN object_category VARCHAR(80);
ALTER TABLE turba_objects ADD COLUMN object_url VARCHAR(255);
CREATE INDEX turba_email_idx ON turba_objects (object_email);
CREATE INDEX turba_firstname_idx ON turba_objects (object_firstname);
CREATE INDEX turba_lastname_idx ON turba_objects (object_lastname);

and now everything is working fine.
hope it helps this fix.
 
I try to run the patch 2.1_to_2.2_sql_schema.php
but it gave a lot of errors becasue it didnt found the PEAR.php object. I tried to update all the paths but always find another error so I get tired, and I just copy the SQL code and I run it straight away into the database.

Hi Yoel,

you have to find the correct pear directory and call from the pear directory the 2.1_to_2.2_sql_schema.php like:

[root@dummy /usr/share/psa-pear]# php /usr/share/psa-horde/turba/scripts/upgrades/2.1_to_2.2_sql_schema.php

because the reson for the upgrade is not only to alter the tables also to move / split existing entrys to meet the new tables, like transform fullname into lastname and firstname

Brujo
 
Hi Yoel,

you have to find the correct pear directory and call from the pear directory the 2.1_to_2.2_sql_schema.php like:

[root@dummy /usr/share/psa-pear]# php /usr/share/psa-horde/turba/scripts/upgrades/2.1_to_2.2_sql_schema.php

because the reson for the upgrade is not only to alter the tables also to move / split existing entrys to meet the new tables, like transform fullname into lastname and firstname

Brujo

Thanks for the update, it run the upgrade perfect.
 
Any detailed help on this will be perfect!
i get an error DB Error: Connect failed.
 
i get an error DB Error: Connect failed.

I can also confirm this address book DB error, users are also now unable to change their passwords along with a DB error when accessing the calendar! All the above worked without issue before the last update which is a shocking release to the main stream user to say the least.

Whatever happened to beta testing before general release?
 
Any detailed help on this will be perfect!
i get an error DB Error: Connect failed.

To make sure what users got privileges on your Horde database check the databases on your cpanel
then access them via phpMyAdmin, select the horde databse, and check users privileges.

should be admin, and horde

update the admin password on the 2.1_to_2.2_sql_schema.php file.


/* You must set these to an appropriate user/pass/table for your server. */
$db_user = 'admin';
$db_pass = '*******';
$db_table = 'turba_objects';



Note: the user horde can not be used at least you change users privileges on the horde database. and also reset horde's password.
 
Still no success... no error, but the address book is still with DB_error

Any update? My clients are going to EAT me alive.
 
Try to use following workaround:

# cd /usr/share/psa-horde/turba/scripts/upgrades

edit script 2.1_to_2.2_sql_schema.php:

set db_user, db_pass to 'admin' and admin's password.
set var $for_real to true

execute the script:

# php -d include_path=".:/usr/share/psa-pear" 2.1_to_2.2_sql_schema.php

It will upgrade horde.turba_objects properly.
 
@IgorG: Your suggestion doesn't solves the problem to me: after the successfull upgrade of the horde.turba_objects still the error message "DB Error: no such field" remains when using the horde web calendar application.
 
Yes, same problem here - I've got some real unhappy people on the other end of the phone.
 
Problem will be completely fixed in Plesk 9.5.2 version which will be released very very soon.
 
What is "very very soon" we talking a week? A month? And then we get to upgrade again - what can we expect to break after doing this upgrade?

Is there was way to access the calendar database, and pull out the information I need to appease those who have their lives scheduled on that calendar. They need it to operate their business.
 
Back
Top