Moving appointments in Google calendar drops reminder



8 years ago
7 years ago


(Reporter: tims-mozilla, Unassigned)





8 years ago
User-Agent:       Opera/9.80 (Windows NT 5.1; U; en) Presto/2.2.15 Version/10.10
Build Identifier: 2008091719

I use Lightning to access my Google calendar.
When I create an appointment and set a reminder for it that works fine.  However, when I then re-open that appointment and change anything (date, time, name, etc) the reminder is lost, even though the same reminder time is still selected.  This also happens when dragging the appointment to a different day.  

Reproducible: Always

Steps to Reproduce:
1. Create event with reminder
2. Re-open the event and change anything, then save and close
3. Watch the reminder disappear
Actual Results:  
The reminder is lost

Expected Results:  
The reminder remains the same

This only happens with the Provider for Google Calendar.  It does not when dealing with events in the local Lightning calendar.  I'm currently using Google provider version 0.5.6
Sounds like you are using Lightning 0.9. Please upgrade to 1.0b1 and the Provider 1.0b1 and retest. I had no trouble with the latest version.

Comment 2

8 years ago
I upgraded Lightning to 1.0b1 and Google Provider v 0.6b1 (I couldn't find 1.0.b1 as you suggested, and the nightly build wouldn't install).  The same problem happens.  
One additional piece of information: Once I move an appointment from one day to another, not only is the reminder lost, but I cannot set another one either.  If I open the newly moved event and set a reminder and close it, it saves and closes but does not save the reminder.
tims-mozilla, is this still an issue using the recently released Lightning 1.0 and Provider for Google Calendar 0.9?

Comment 4

7 years ago
Issue appears to be resolved with Lightning 1.0/Google 0.9.
Thank you.
tims-mozilla, thanks for your response! Resolving as WORKSFORME.
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.