Closed Bug 1481043 Opened 7 years ago Closed 7 years ago

Reminders on local calendars are not correctly loaded when using the gdata provider

Categories

(Calendar :: Provider: GData, defect)

Lightning 6.2
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
6.2.2.1

People

(Reporter: Fallen, Assigned: Fallen)

References

Details

Attachments

(1 file)

STR: 1) install gdata provider 2) create local calendar with default alarm 3) open event again Result: * Event dialog is set to "no reminders" Expected: * Event dialog should be set to the default alarm
Attached patch Fix - v1 โ€” โ€” Splinter Review
Attachment #8997709 - Flags: review?(makemyday)
Attachment #8997709 - Flags: approval-calendar-esr+
Attachment #8997709 - Flags: approval-calendar-beta+
Comment on attachment 8997709 [details] [diff] [review] Fix - v1 Review of attachment 8997709 [details] [diff] [review]: ----------------------------------------------------------------- Thanks, r+ That's the same issue as in bug 1480397, I assume?
Attachment #8997709 - Flags: review?(makemyday) → review+
Additional information: * Same problem happens whether I use the default reminder (mine is set at 3 hours), one of the default values in a menu (say, 2 hours) or a custom value. * Problem occurs with Provider 4.4 and 4.4.1 (both on TB 52.9 and TB 60), but not with Provider 3.3 (TB 52.9). * Problem happens with reminders set on ALL calendars: Google calendars, local calendars and a CalDav calendar used in my office. * With Google calendars and the CalDav calendar (I can't check with a local calendar), if I create an event with all its details and set an alarm, the alarm automatically reverts to "no alarm". If I "save and close" it immediately, the alarm is remembered (I can see it in Google). If I re-open the event to update it (ex.: add a few details), the alarm is removed.
Philipp, this change seems to have already landed with the patch from bug 1481154. We should resolve this bug as FIXED with target 6.2, although I am not entirely sure how to read the branching/versioning concerning a version 6.2.1 or 6.2.0.1.
Flags: needinfo?(philipp)
This is going to be part of 4.4.2. I'm not sure we should worry about the exact milestone, gdata releases are currently piecemeal from comm-central plus a few patches to undo comm-central stuff not compatible with 52. I'm considering moving it to github altogether.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(philipp)
Resolution: --- → FIXED
Target Milestone: --- → 6.2.1
Comment on attachment 8997709 [details] [diff] [review] Fix - v1 Nothing to uplift here.
Attachment #8997709 - Flags: approval-calendar-esr+
Attachment #8997709 - Flags: approval-calendar-beta+
Target Milestone: 6.2.1 → 6.2.2
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: