Important note for all syncml users. please read!

jaytraxx 2010-02-03 18:18:55 UTC #1

IMPORTANT NOTE FOR ALL SYNCML USERS. PLEASE READ!

I’ll keep this message short, in the hope it will be read:

All users who sync their devices with SyncML have to be aware that an
"initial sync" will be necessary on any synced device directly after the
next update of an EGroupware instance.

GroupDAV devices should be updated automatically and there are no
further things to do for GroupDAV devices.

Which updates are affected?

Updates from any official version <= 1.6.002

to future 1.6.003
to current SVN versions [branch (Revision ) or trunk (Revision )]

Updates from any SVN version

to current SVN version [branch (Revision ) or trunk (Revision )]

Reason:
In current EGroupware versions (<= 1.6002) we did not fully match the
iCal RFC on calendar entries. This caused some hard to resolve problems
for syncing the calendar entries. With the next update we change the
contents of the calendar’s UID and RECURRENCE-ID database fields to fit
the iCal RFC.

Here’s some advice on performing the next EGroupware update:

let your SyncML users perform a last sync before EGroupware gets updated
tell your users to not change any entries on the sync devices until
the update is finished
after the update, let your users perform an “initial sync” on every
device; this means to let the sync remove all the contents on the device
and refresh it with the server data; this can be done by a setting on
your device

We’ll place some further reminders for you on the mailing list and
website when future 1.6.003 or the very future 1.8 versions will be
released.

Greetings
christian

The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

jaytraxx 2010-02-03 18:27:11 UTC #2

Sorry, I forgot to add an important info regarding the affected SVN
revision numbers before, so I’ll post this part again:

Which updates are affected?

Updates from any official version <= 1.6.002

to future 1.6.003
to current SVN versions [branch (Revision 29097) or trunk (Revision
29096)]

Updates from any SVN version

to current SVN versions [branch (Revision 29097) or trunk (Revision
29096)]

Greetings
christian

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

ChristophK 2010-02-04 09:53:01 UTC #3

Hi Christian,

this affects the addressbook as well, or only infolog and calendar?

Christoph

IMPORTANT NOTE FOR ALL SYNCML USERS. PLEASE READ!

I’ll keep this message short, in the hope it will be read:

All users who sync their devices with SyncML have to be aware that an
"initial sync" will be necessary on any synced device directly after the
next update of an EGroupware instance.

GroupDAV devices should be updated automatically and there are no
further things to do for GroupDAV devices.

Which updates are affected?

Updates from any official version <= 1.6.002

to future 1.6.003

to current SVN versions [branch (Revision ) or trunk (Revision )]

Updates from any SVN version

to current SVN version [branch (Revision ) or trunk (Revision )]

Reason:
In current EGroupware versions (<= 1.6002) we did not fully match the
iCal RFC on calendar entries. This caused some hard to resolve problems
for syncing the calendar entries. With the next update we change the
contents of the calendar’s UID and RECURRENCE-ID database fields to fit
the iCal RFC.

Here’s some advice on performing the next EGroupware update:

let your SyncML users perform a last sync before EGroupware gets updated

tell your users to not change any entries on the sync devices until
the update is finished

after the update, let your users perform an “initial sync” on every
device; this means to let the sync remove all the contents on the device
and refresh it with the server data; this can be done by a setting on
your device

We’ll place some further reminders for you on the mailing list and
website when future 1.6.003 or the very future 1.8 versions will be
released.

Greetings
christian

— The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the
business Choose flexible plans and management services without long-term
contracts Personal 24x7 support from experience hosting pros just a phone
call away. http://p.sf.net/sfu/theplanet-com

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

jaytraxx 2010-02-04 11:07:13 UTC #4

Hi Christoph,

it just affects calendar.

Greetings
christian

Christoph Kaulich:

Hi Christian,

this affects the addressbook as well, or only infolog and calendar?

Christoph

Am Mittwoch, 3. Februar 2010 19:18:55 schrieb Christian Binder:

IMPORTANT NOTE FOR ALL SYNCML USERS. PLEASE READ!

I’ll keep this message short, in the hope it will be read:

All users who sync their devices with SyncML have to be aware that an
"initial sync" will be necessary on any synced device directly after the
next update of an EGroupware instance.

GroupDAV devices should be updated automatically and there are no
further things to do for GroupDAV devices.

Which updates are affected?

Updates from any official version <= 1.6.002

to future 1.6.003

to current SVN versions [branch (Revision ) or trunk (Revision )]

Updates from any SVN version

to current SVN version [branch (Revision ) or trunk (Revision )]

Reason:
In current EGroupware versions (<= 1.6002) we did not fully match the
iCal RFC on calendar entries. This caused some hard to resolve problems
for syncing the calendar entries. With the next update we change the
contents of the calendar’s UID and RECURRENCE-ID database fields to fit
the iCal RFC.

Here’s some advice on performing the next EGroupware update:

let your SyncML users perform a last sync before EGroupware gets updated

tell your users to not change any entries on the sync devices until
the update is finished

after the update, let your users perform an “initial sync” on every
device; this means to let the sync remove all the contents on the device
and refresh it with the server data; this can be done by a setting on
your device

We’ll place some further reminders for you on the mailing list and
website when future 1.6.003 or the very future 1.8 versions will be
released.

Greetings
christian

— The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the
business Choose flexible plans and management services without long-term
contracts Personal 24x7 support from experience hosting pros just a phone
call away. http://p.sf.net/sfu/theplanet-com

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

Hans-Jurgen_Tappe 2010-02-04 11:34:55 UTC #5

Hi Christian!

Christian Binder schrieb:

In current EGroupware versions (<= 1.6002) we did not fully match the
iCal RFC on calendar entries. This caused some hard to resolve problems
for syncing the calendar entries. With the next update we change the
contents of the calendar’s UID and RECURRENCE-ID database fields to fit
the iCal RFC.

Would this be a good time to unify the IDs between tasks and calendar
entries in order to finally make icalsrv superfluous for synchronization?
Now, that the IDs change anyway… Is there a plan to do that or is this
change already done with that in mind?

Best regards,
Hans-Jürgen

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

rkraemer 2010-02-04 11:37:43 UTC #6

Hallo, nach dem Update werden die Kategorien in Lightning per groupdav.php nicht mehr angezeigt, bzw. werden nicht gespeichert. In egruopware sind sie allerdings sichtbar. Kalender und Aufgaben in Lightning per icalsrv.php funktioniert nach wie vor nicht.

Gruß, Robert

jaytraxx:

IMPORTANT NOTE FOR ALL SYNCML USERS. PLEASE READ!

I’ll keep this message short, in the hope it will be read:

All users who sync their devices with SyncML have to be aware that an
"initial sync" will be necessary on any synced device directly after the
next update of an EGroupware instance.

GroupDAV devices should be updated automatically and there are no
further things to do for GroupDAV devices.

Which updates are affected?

Updates from any official version <= 1.6.002

to future 1.6.003

to current SVN versions [branch (Revision ) or trunk (Revision )]

Updates from any SVN version

to current SVN version [branch (Revision ) or trunk (Revision )]

Reason:
In current EGroupware versions (<= 1.6002) we did not fully match the
iCal RFC on calendar entries. This caused some hard to resolve problems
for syncing the calendar entries. With the next update we change the
contents of the calendar’s UID and RECURRENCE-ID database fields to fit
the iCal RFC.

Here’s some advice on performing the next EGroupware update:

let your SyncML users perform a last sync before EGroupware gets updated

tell your users to not change any entries on the sync devices until
the update is finished

after the update, let your users perform an “initial sync” on every
device; this means to let the sync remove all the contents on the device
and refresh it with the server data; this can be done by a setting on
your device

We’ll place some further reminders for you on the mailing list and
website when future 1.6.003 or the very future 1.8 versions will be
released.

Greetings
christian

The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

jaytraxx 2010-02-04 12:59:54 UTC #7

Hi Hans Jürgen,

… I don’t know what you mean. Could you make an example please? For the SyncML Part: There’s no problem with the tasks from my point of view, so you could regard icalsrv superflous anyway … or did I miss something?

Greetings
christian

jaytraxx 2010-02-04 13:03:38 UTC #8

Hi Robert,

That could be a side-effect for the last changes in the ical code. I can’t imagine that this has something to do with the DB upgrade or is it possible to reconstruct that problem exactly with the revision of the db update?

I don’t mind for icalsrv.php, sorry. As far as I know, it’s not maintained anymore (correct me if I’m wrong).

Greetings
christian

Hans-Jurgen_Tappe 2010-02-04 16:22:21 UTC #9

Hi Christian!

jaytraxx schrieb:

Hans-Juergen Tappe wrote:

Would this be a good time to unify the IDs between tasks and calendar
entries in order to finally make icalsrv superfluous for synchronization?
Now, that the IDs change anyway… Is there a plan to do that or is this
change already done with that in mind?
… I don’t know what you mean. Could you make an example please? For the
SyncML Part: There’s no problem with the tasks from my point of view, so you
could regard icalsrv superflous anyway … or did I miss something?

Ralph told me that for the tasks support via the groupdav frontend, the
uniqueness of IDs must span both calendar events and infologs. For
display of tasks in thunderbird lightning, It still requires icalsrv, as
far as I can see.

But maybe, we can also use a different approach (like a prefix) for
groupdav? Sorry, I am not deep into the synchronization subject. It
just seemed like a good time to change the groupdav IDs now - if they are
also changed for syncML now.

Best regards,
Hans-Jürgen

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

jaytraxx 2010-02-08 21:41:25 UTC #10

Hi Hans-Jürgen,

Hans-Juergen Tappe schrieb:

Ralph told me that for the tasks support via the groupdav frontend, the
uniqueness of IDs must span both calendar events and infologs. For
display of tasks in thunderbird lightning, It still requires icalsrv, as
far as I can see.

But maybe, we can also use a different approach (like a prefix) for
groupdav? Sorry, I am not deep into the synchronization subject. It
just seemed like a good time to change the groupdav IDs now - if they are
also changed for syncML now.

That’s really completely new for me. Maybe Ralf can give an advice on
this ??

Best regards,
Hans-Jürgen

The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers

jaytraxx 2010-03-12 07:38:37 UTC #11

This thread is important for all SyncML users who plan to upgrade to the current 1.6.003 release. I’ll put that note into the 1.6.003 release notes soon.

Ralf_Becker_Stylite 2010-03-13 09:33:35 UTC #12

Hi Christian,

jaytraxx schrieb:

This thread is important for all SyncML users who plan to upgrade to the
current 1.6.003 release. I’ll put that note into the 1.6.003 release notes
soon.

Thanks

Ralf Becker
Director Software Development

Stylite GmbH
[open style of IT]

Morschheimer Strasse 15
67292 Kirchheimbolanden

fon +49 (0) 6352 70629-0
fax +49 (0) 6352 70629-30
mailto: rb@stylite.de

www.stylite.de
www.egroupware.org

Geschäftsführer Andre Keller,
Gudrun Müller, Ralf Becker
Registergericht Kaiserslautern HRB 30575
Umsatzsteuer-Id / VAT-Id: DE214280951

Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers