• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Migration horde parameter FAILED!

sebgonzes

Silver Pleskian
Hello

We recientely migrate data from plesk 17.0 to 17.5.3, and ALL configuration of horde clients have been lost! NO calendar, NO contact list, NO horde rules, NO signature....

Please, need an solution ASAP!
 
Roundcube and Horde databases often change their structure, so we never include them in the backup and never migrate them. There are can be serious problems when you restore Roundcube/Horde database from the old version to the new/updated Roundcube/Horde version on Plesk server.
 
Roundcube and Horde databases often change their structure, so we never include them in the backup and never migrate them. There are can be serious problems when you restore Roundcube/Horde database from the old version to the new/updated Roundcube/Horde version on Plesk server.

You MUST give an solution to this problem (and much more now that you have increase licence price!), or better delete these webmail!

If you include them, client use all funcionality available, and it's not possible to say her that all parameters (include contact list!!!!) have been deleted due to increase version of product! It's very NOT an serious answer from the as plesk want to say "better panel control"...
 
You MUST give an solution to this problem
For example, solution for Roundcube Address Book - How to migrate Roundcube address books?
The problem in that Horde or Roundcube does not provide any tools for migration their specific settings/plugins/etc. If you think that Plesk should create these tools for third-party software, you can create feature request in Plesk UserVoice. At the moment, you can perform these migrations manually.
 
For example, solution for Roundcube Address Book - How to migrate Roundcube address books?
The problem in that Horde or Roundcube does not provide any tools for migration their specific settings/plugins/etc. If you think that Plesk should create these tools for third-party software, you can create feature request in Plesk UserVoice. At the moment, you can perform these migrations manually.

Thanks for so good solution when we are talking about a lot of domain...
 
The problem/bug will be the same upgrading an server from plesk 17.0.17 to plesk 17.5.3?
When you perform upgrade, corresponding webmail package will be upgraded with upgrading the same webmail database. The problem only is in moving webmail database.
 
When you perform upgrade, corresponding webmail package will be upgraded with upgrading the same webmail database. The problem only is in moving webmail database.

And really plesk team is not able to review change and adapt it??? You realize that this affect also contact list??? not just configuration that can be reconfigurated by client, but also data!
So to resume, horde is able to adapt his database to new versions, but Plesk team is not able to do it in migration...
 
You could always try updating Horde on the old server and then moving the database across.... You'll just want the Horde versions to match so you know the database structure is the same.
 
You could always try updating Horde on the old server and then moving the database across.... You'll just want the Horde versions to match so you know the database structure is the same.

In our case, this not could work as we join various small server to one more big server (yes, reducing the plesk licence number...), so horde/roundcube database can't be dumped from old server and restored on new server in each case, id's can be not the same in each databases.
I still considerate a shame that plesk still don't put any solution to this problem... Contact have an export system in both system (roundcube/horde), so why plesk team is not able to use it? Also can be do directly by databases, but seem it's an too big effort for plesk team (it's an bug that we have since plesk8!)
 
We can not and will not offer solutions if the third-party software vendor does not have it. Similarly, we will never support alpha and beta versions of vendor's software. For example, if Centos does not offer a dist-upgrade, unlike Ubuntu or Debian, then we do not support it either but support for Debian and Ubuntu.
 
We can not and will not offer solutions if the third-party software vendor does not have it. Similarly, we will never support alpha and beta versions of vendor's software. For example, if Centos does not offer a dist-upgrade, unlike Ubuntu or Debian, then we do not support it either but support for Debian and Ubuntu.
Sorry, but both webmail (roundcube and horde) have export contact, option, so YES software have this option, why plesk don't offer it in the migration so?
 
Back
Top