Published calendars do not update on server
I have successfully published my calendar to a WebDAV server, and Outlook users can sucessfully subscribe to my calendar.
However, when I add events to my calendar the server .ics file does not get updated. It still has the same timestamp as when it was first published.
How can I fix this?
All Replies (5)
you need to publish as caldav, not webdav. an ICS file is not read write, only read.
Matt - I am starting to experiment with CalDAV (actually DaviCal) now. However, I am using these calendars in an MS Outlook environment which only supports WebDAV. The subscribers to my WebDAV calendar do not update them, but the owner/publisher of the calendar (me) should be able to do so. In fact, the "publish" operation *can* write to the .ics file on the server because that is how the calendar gets there in the first place.
The issue is: why does Lightning not refresh that calender on the server when I make a change to my own published calendar? It can do that and should do it.
Is this a bug?
Modified
I solved this by creating my own script to interpret the calendar database and create .ics files on the server when there are changes. See https://support.mozilla.org/en-US/questions/1103992
I think it's a bug for Lightning to *not* update the server WebDAV calendars when the publisher makes changes to his/her calendar. This makes the "publish" function identical to the "export" function.
WebDAV calendars are not read-only. They are read-only to the calendar subscribers, but the publisher should be able to have the server resident calendar updated when local calendar changes are made. This is not happening with Lightning ... BUG!
MarkFoley said
I solved this by creating my own script to interpret the calendar database I think it's a bug for Lightning to *not* update the server WebDAV calendars when the publisher makes changes to his/her calendar. This makes the "publish" function identical to the "export" function.
Have you filed a bug? https://bugzilla.mozilla.org/
I suggest you do if you have not.
Modified
Done. Bug 1241395