I'm not sure you can be any "sooner" than right now - it already is in the Edge version.
I don't have any guesstimate on when it may move through the tiers, as things can stay in Edge for several weeks.
I don't have any guesstimate on when it may move through the tiers, as things can stay in Edge for several weeks.
Thank you, I do have some users that are resistant to change and this is sure to be a thorn in my side. I do understand the reasoning and prefer they be using RC anyway.
We are currently set to RELEASE, if I was to switch to STABLE will that give my users a bit more time to acclimate to RC?
Also, is it safe to say the migration from Horde (contacts and calendar) to RC is full operational if this is in EDGE?
We are currently set to RELEASE, if I was to switch to STABLE will that give my users a bit more time to acclimate to RC?
Also, is it safe to say the migration from Horde (contacts and calendar) to RC is full operational if this is in EDGE?
Moving to Stable would definitely give you the most time to put off that change as that is the last version it'll get pushed to. While I'm not sure when that will be, it will be sometime before the end of this year if everything goes as planned.
The Horde -> Roundcube migration tools are the one thing keeping Edge from being pushed through the tiers right now, as they are not quite complete yet.
The Horde -> Roundcube migration tools are the one thing keeping Edge from being pushed through the tiers right now, as they are not quite complete yet.
It's always a tough call as to how many warnings we put in the interface, and where they get displayed. Usually when we do that, there is backlash from admins and users as some people think it's too confusing or intrusive.
108 is likely going to move to Current as soon as the Horde migration tools are ready, which I would expect to be within the next few weeks. I would plan on it making it to the Stable tier by the end of the year.
108 is likely going to move to Current as soon as the Horde migration tools are ready, which I would expect to be within the next few weeks. I would plan on it making it to the Stable tier by the end of the year.
@cPRex Thanks for the update 
Meanwhile, could you confirm existing calendars and contacts included shared calendars/contacts will be migrated to v108? We did some tests on the EDGE version and we noticed migration was far from being complete... no shared calendar/contact was available in RoundCube after updating to v108 which is unacceptable for our userbase. I know this is still work-in-progress but I'd like to ensure this use-case was not forgotten and that cPanel will keep its promise to migrate all contacts/calendars to RoundCube
Also, I don't want to interfere with your roadmap, but couldn't you keep Horde for customers using Cloudlinux-supported PHP 7.4?
Meanwhile, could you confirm existing calendars and contacts included shared calendars/contacts will be migrated to v108? We did some tests on the EDGE version and we noticed migration was far from being complete... no shared calendar/contact was available in RoundCube after updating to v108 which is unacceptable for our userbase. I know this is still work-in-progress but I'd like to ensure this use-case was not forgotten and that cPanel will keep its promise to migrate all contacts/calendars to RoundCube
Also, I don't want to interfere with your roadmap, but couldn't you keep Horde for customers using Cloudlinux-supported PHP 7.4?
@julienmru - yes, the migration of the calendars is one of the things keeping 108 from being moved to Release. Once that's ready to go, it will make its way through the tiers, which I am expecting to happen in January.
The Horde issue isn't related to CloudLinux PHP, but to internal PHP used by cPanel. cPanel has a separate internal PHP system - you'll notice that if you kill Apache on your server, the WHM and cPanel interfaces continue to operate normally.
The Horde issue isn't related to CloudLinux PHP, but to internal PHP used by cPanel. cPanel has a separate internal PHP system - you'll notice that if you kill Apache on your server, the WHM and cPanel interfaces continue to operate normally.
I just did a new test again on this.
First time the migration didn't end well, but that was because RoundCube was using MySQL and not SQLite. So this time I converted all accounts to SQLite first.
But the upgrade to version 108 should do this automatically, convert RC from MySQL to SQLite before export/import of calendars/contacts.
Everything I tested was exported/imported, but noticed some bugs:
First time the migration didn't end well, but that was because RoundCube was using MySQL and not SQLite. So this time I converted all accounts to SQLite first.
But the upgrade to version 108 should do this automatically, convert RC from MySQL to SQLite before export/import of calendars/contacts.
Everything I tested was exported/imported, but noticed some bugs:
- Address book was imported, but they are all in the same address book. Not in 2 as they were in Horde.
- Calendar events were duplicated. So all events were migrated to RC, but they are all duplicates. This must be fixed and should be easy to fix before releasing the version.
- Calendar events were given a new creation date/time. Not sure this can fixed in an easy way and that's not that important either. But if it can be fixed it would be great.
Hello @Hedloff
Thank you for this report. I'm the new Product Owner for the team that is performing this work, I've put the case that @cPRex opened on the team's backlog, but I did want to get clarity on the first bullet you have here:
Can you expand on this? I'm curious about the use case for having multiple address books for a cPanel user. What makes this a necessary feature, as shared contacts are not a function that Roundcube supports right now I'm trying to understand how important this feature is.
Thanks!
I have never used it myself and don't think many customers use many different address books in Horde either. So I don't think you should use too much energy on that.
But for " Calendar events were given a new creation date/time." it would be better to get fixed. What about recurring events for example?
Would be great if you got fixed CPANEL-42200 asap, then we will upgrade all servers and get Horde removed.
Thanks for that, we are working on the other issues, and I can let you know here when they are resolved. I just wanted to understand the multiple address book concern better to make sure we weren't missing something that was important.
Thank you!
We did some more testing on CPANEL-42200 issue and seems like it's just showing duplicates in RoundCube, not in Thunderbird or other CalDAV clients such as Android.
Hello @cPanelLauren,
Could you confirm shared contacts and shared calendars will indeed be available in v108's Roundcube?
Sorry for the message if it's not relevant, but I prefer to be safe than sorry; my understanding of your message made me think shared contacts were not supported.
Thanks!
We have customers who use the shared address book in Horde and this is going to be a regression if we don't have it when v108 ships. I already informed the support about it a while back (request #94491459) but I'm not sure it made its way to your backlog.
Could you confirm shared contacts and shared calendars will indeed be available in v108's Roundcube?
Sorry for the message if it's not relevant, but I prefer to be safe than sorry; my understanding of your message made me think shared contacts were not supported.
Thanks!
Hello,
You'll still be able to share calendars with CCS but the functionality that allowed shared address books goes away with the horde removal. I realize that is not the best news, but unfortunately, we had no choice but to remove horde due to lack of new development including the support of modern versions of PHP. We are looking to include this functionality moving forward but I cannot guarantee it.
Hello,
Also, I'm not the lead developer on the project but I know you can connect CardDAV to Roundcube, eg. with the roundcube/carddav package. I would really appreciate you consider taking the necessary steps to keep the "business as usual" promise when switching to Roundcube.
Last but not least, I understand cPanel uses a specific PHP version but could you consider using Cloudlinux's supported PHP version for users who have Cloudlinux to be able to keep Horde? I understand that would require some changes, at least, that would prevent a regression and buy your team more time to deliver on the promise.
Thanks : )
This regression will certainly cause headaches and cPanel always insisted calendar and contacts will be migrated:
But that's sadly not the case : (
Also, I'm not the lead developer on the project but I know you can connect CardDAV to Roundcube, eg. with the roundcube/carddav package. I would really appreciate you consider taking the necessary steps to keep the "business as usual" promise when switching to Roundcube.
Last but not least, I understand cPanel uses a specific PHP version but could you consider using Cloudlinux's supported PHP version for users who have Cloudlinux to be able to keep Horde? I understand that would require some changes, at least, that would prevent a regression and buy your team more time to deliver on the promise.
Thanks : )
