CalDAV: SEQUENCE attribute not updated on calendar entry edit #27151

hirschnase opened this Issue Feb 14, 2017 · 0 comments


None yet

1 participant

hirschnase commented Feb 14, 2017 edited

Steps to reproduce

(in the owncloud calendar web-interface)

  1. create a calendar entry
  2. edit the entry (multiple times)
  3. get the caldav event object and have a look at the "sequence" attribute - is always 0

Expected behaviour

SEQUENCE should be updated (incremented) on each calendar entry edit, according to the CalDAV spec.

"The server MUST ensure that for each type of scheduling operation, the "SEQUENCE" iCalendar property value is updated as per iTIP [RFC5546]."

Actual behaviour

SEQUENCE is not being updated and always set to 0.

Server configuration

Operating system:

Web server:


PHP version:

ownCloud version: (see ownCloud admin page)

Updated from an older ownCloud or fresh install:
Updated from 8.0.2

Example calendar event object dump where "sequence=>0"

#<Icalendar::Event:0x000000073b2458 @name="VEVENT", @components={:alarms=>[#<Icalendar::Alarm:0x000000073da278 @name="VALARM", @components={}, @properties={"action"=>"AUDIO", "x_wr_alarmuid"=>["BDFC4804-4927-43C7-BE43-672DF51B9154"], "uid"=>"BDFC4804-4927-43C7-BE43-672DF51B9154", "trigger"=>"-PT15H", "x_apple_default_alarm"=>["TRUE"], "attach"=>[#<URI::Generic:0x000000073e6640 URL:Basso>]}>]}, @properties={"sequence"=>0, "dtstamp"=>Thu, 09 Feb 2017 16:36:31 +0000, "created"=>Fri, 03 Feb 2017 08:14:04 +0000, "uid"=>"0fec55d981", "transp"=>"OPAQUE", "x_apple_travel_advisory_behavior"=>["AUTOMATIC"], "summary"=>"test 123", "last_modified"=>Fri, 03 Feb 2017 08:14:04 +0000, "location"=>"here and there", "ip_class"=>"PUBLIC", "status"=>"CONFIRMED", "dtstart"=>Wed, 21 Dec 2016, "dtend"=>Sat, 24 Dec 2016}>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment