SyncKolab 3

Mihai Badici mihai at badici.ro
Thu Jun 27 23:03:55 CEST 2013


On Wednesday 22 May 2013 14:24:23 you wrote:

    
>It should work with the current      nightly. I fixed everything I could find 
>but I didnt have time to      test it completely yet.
      
>      Chec kout the new nightly and maybe write a bug report if it still      
>does not work.
      


I tried to find why calendar is still not working in synckolab.

I find this error in webserver's log:
error: element 'dtstart' is not allowed for content model 
'(uid,created,dtstamp,sequence?,class?,categories?,dtstart?,dtend?,duration?,transp?,rrule?,rdate?,exdate?,recurrence-
id?,summary?,description?,priority?,status?,location?,organizer?,attendee*,attach*,x-
custom*)'
Critical: /root/libkolabxml-master/src/xcalconversions.h 1878:   Failed to 
parse calendar!


So it looks like an inconsistency in kolab3 format.
I tried to compare the object with one created by roundcube and all I can find 
is there are some attributed missing, like "created", "dtstamp" and few 
others.
Also I noticed in roundcube dtstart time does not end in "Z" ( but creation 
time does). In roundcube, the dtstart contains also the timezone.
I don't manage to find a good description of kolab3 schema for calendar to 
explain that error.



The content of the file is:

To: synckolab at no.tld
Subject: 8EE37597130DCCBF6F8F4657536699EB-0CF04A5582A02933
Date: Thu, 27 June 2013 23:20:51 +0300
MIME-Version: 1.0
Content-Type: Multipart/Mixed;boundary="Boundary-00=B22469CC18104DAE"
User-Agent: SyncKolab 3.1.1
X-Kolab-Type: application/x-vnd.kolab.event

--Boundary-00=B22469CC18104DAE
Content-Type: Text/Plain;
 charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is a Kolab Groupware object.
To view this object you will need an email client that can understand the 
Kolab Groupware format.
For a list of such email clients please visit
http://kolab.org/content/kolab-clients
---
Summary: test1
---

Notice:
The information above is only valid, if no other client than synckolab updated 
this message. (ie. a client that updates the attachment but not the message)

--Boundary-00=B22469CC18104DAE
Content-Type: application/calendar+xml;
 name="kolab.xml"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="kolab.xml"

<?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"no" ?>=0A<icalendar =
xmlns=3D"urn:ietf:params:xml:ns:icalendar-2.0">=0A<vcalendar>=0A<properties=
>=0A <prodid><text>Synckolab , Calendar Sync</text></prodid>=0A <version><t=
ext>2.0</text></version>=0A <x-kolab-version><text>3.0</text></x-kolab-ve=
rsion>=0A</properties>=0A<components><vevent>=0A<properties>=0A  <uid><text=
>8EE37597130DCCBF6F8F4657536699EB-0CF04A5582A02933</text></uid>
<dtstart><date-time>2013-06-27T10:00:00Z</date-time></dtstart>=0A  
<dtend><date-ti=
me>2013-06-27T11:00:00Z</date-time></dtend>=0A  <summary><text>test1</text>=
</summary>=0A  <x-custom-sensitivity><text>public</text></x-custom-sensitiv=
ity>=0A  <x-custom-show-time-as><text>busy</text></x-custom-show-time-as>=
=0A </properties>=0A</vevent>=0A</components></vcalendar></icalendar>
--Boundary-00=B22469CC18104DAE--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20130628/247cd2d0/attachment.html>


More information about the users mailing list