-
Notifications
You must be signed in to change notification settings - Fork 57
"Invite Attendees" makes calendar read-only #63
Comments
Hi @logological, can you please turn on logging in preferences and see if there is any relevant information in there that would help better understand this issue? I would assume there is an error returned by the server that the add-on does not expect. Fixing this root cause would be easier than implementing a mitigation strategy. |
I turned on logging at the "basic information" level for the core provider, communication with the Exchange server, and addressbook/contacts. Creating an event and inviting one person ends up producing 725 logging messages. None of them seem like obvious relevant, errors to me. Can you give me some more ideas of what I should be looking for exactly? |
I am seeing this as well with the invite attendees. I also see it with the Out of Office functionality. This is with v4.0.0-beta6. The Out of Office seems to repeatedly ask for a password. I'll attempt to get logs requested. |
The first error (Mutation Events) happened once I went into the "Invite Attendees" section The .onBlurInput errors came from me tabbing between the invitee boxes (where you can add people to the meeting in the Invite Attendees screen) The POST error came up while I was entering things. When I waited 30-60 seconds the event saved without issue, and the invites were sent to the respective individuals. |
Same issue here:
Waiting for 30-60 seconds (until the read-only lock disappears) before clicking on "Save and close" works as workaround as already described by @jeffcorcoran. |
Whenever I invite attendees to an event, my calendar becomes read-only for about 30 to 60 seconds. This means it's impossible for me to immediately save and close the event. If I try to do so anyway, I get a rather unhelpful MODIFICATION_FAILED error message, and my new event is lost.
Steps to reproduce:
Observed behaviour:
5. The calendar becomes read-only. (This is evident only if you are in the Calendar tab; a lock icon will appear next to the calendar.) The calendar remains read-only for about 30 to 60 seconds. If you attempt to save the event during this period, you get a nondescript error dialog; pressing the "Details" button shows only "MODIFICATION_FAILED".
Expected behaviour:
5. The calendar should not become read-only. If for some reason this is absolutely unavoidable, then attempting to save the event should result in a meaningful error dialog, which should return the user to the event dialog rather than discarding the event.
The text was updated successfully, but these errors were encountered: