Frequent "Element was modified while you were editing it" errors

[Aaron Williamson]

I've been getting these errors regularly from AgenDAV when trying to modify an event I recently created (even where "recently" = "last night"). I'm using radicale as my caldav server. The error is coming from web/application/controllers/event.php (this error is used in 4 places in event.php, but for me it's always the first instance @ line 414). I don't know much about what the code is doing here -- any thoughts on what may be causing this?

[Jorge López Pérez]

Hi Aaron,

I have just answered your issue at GitHub, hope it helps:

https://github.com/adobo/agendav/issues/55 .

Regards.

El 04/09/12 15:54, Aaron Williamson escribió:

--
Jorge López Pérez
http://adobo.org
Jabber: jor...@jabberes.org

[ziegl...@googlemail.com]

Hi,

getting the same error with Bedework.

Did you fix your version?

Would be nice if you could give advice on how to.

Regards.

Oli

[ziegl...@googlemail.com]

Ok, just figured out it's a Problem just with Bedework as my iCal on Mac can't modify events either.

Will try the new Version (V3.9) of Bedework.

@Jorge: This might also be the Problem in my other post with editing the Calendarname and -color.

Btw: deleting and adding new events is no problem, so if the new Version of bedework will not work on this issue, could there be an "workaround" by just deleting the event (wich should be modified) and adding a new event (with updated data of the old), or is this just too much work to be done?

regards Oli

[ziegl...@googlemail.com]

Just got Time to test the new Version of Bedework (3.9).

The Problems with getting an Error when editing events seems solved now (I don't get these Errormessages since updating Bedework).

Still left are the Errors when editing a Calendar (the name or color)

Would be nice if someone could figure out why there is this error.

It's way out of my scope how this happens.

Regards

oli

[Jorge López Pérez]

Hi,

El 01/02/13 16:55, ziegl...@googlemail.com escribió:

> @Jorge: This might also be the Problem in my other post with editing the
> Calendarname and -color.
>
> Btw: deleting and adding new events is no problem, so if the new Version
> of bedework will not work on this issue, could there be an "workaround"
> by just deleting the event (wich should be modified) and adding a new
> event (with updated data of the old), or is this just too much work to
> be done?

If you're getting the 'Element was modified while you were editing it'
message it means that your server rejected the modification request.
AgenDAV requests etags when fetching your calendar events, so modifying
an event implies adding an 'If-Match: (etag)' to the modification request.

If the CalDAV server rejects this request it could be because:

a) The element was modified by another CalDAV client, so etags don't
match anymore

b) Your CalDAV server is doing something wrong with etags

Your problem seems to be the second one. Bedework isn't doing what it
should with etags.

When removing an event AgenDAV forces etags matching, so your suggestion
wouldn't work either. Removing an event without checking etags would be
really dangerous.

Regards.

--
Jorge López Pérez
http://adobo.org

jabber: jor...@jabberes.org