A newer version of SabreDav was used, and the endpoints all changed to use the SugarCRM api rather than custom endpoints.
It was effectively a full re-write.
The documentation was updated to reflect the changes required to the endpoints, but if you have problems after upgrading we would recommend removing the module including the database tables, and re-installing from 3.0.8
We missed your replies due to some issue with email. Thank you for the debugging information, we will continue to investigate. Fortunately the event is imported any way.
In order for the sync to know when to display in Thunderbird, it needs the start date. If the Due date is the primary time sensitive field on the record, then simply set the start date and due date to the same value to allow the item to appear in Thunderbird against the date it needs to be done.
Sorry, we meant to contact you sooner...
Unfortunately it would appear that you have misinterpreted our statement where we said that Activities Sync "allows you to access your Sugar calendar from any device that supports the CALDAV protocol" - this does not mean that it synchronizes with Google Calendar, Advent Calendar, or any other "non-CALDAV" client.
Hi, from personal experience we would recommend you try Open Sync for Android as this prompts you to prevent battery saving, which we suspect is what causes the Caldav Sync to fail.
Our Activities Sync has been designed for Sugar and has not been tested with SuiteCRM in any way. We cannot, therefore offer support for non-Sugar systems.
Our Sugar add-ons are designed for Sugar and, as such, have not been tested with SuiteCRM by us in any way. If they work in SuiteCRM then it's a happy coincidence, but we cannot guarantee that they will work with SuiteCRM as we have no idea of what core code may have been added/changed/removed from the standard Sugar code.
Unfortunately we do not have an on-demand instance with Sugar. Would it be possible for you to create a login on an on-demand instance and email the details to support@opacus.co.uk ?
