Closed Bug 401223 Opened 17 years ago Closed 17 years ago

After update from 0.5 to 0.7 -> calendars are deselected, the calendar view is empty

Categories

(Calendar :: Lightning Only, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: andreas.treumann, Unassigned)

References

Details

STEPS TO REPRODUCE:
===================

- start lightning 0.5
- update to lightning 0.7
- restart

RESULT:
=======

- the calendars are deselected
- the callendar view is empty

EXPECTED RESULT:
================

- after the the update the calendars should not deselected

REPRODUCIBLE:
=============

- always
Correct, see <http://www.mozilla.org/projects/calendar/releases/lightning0.7.html#issues>. I guess this is due to the calendar list changes from Bug 388405.

Now that 0.7 is already released I don't see a way to fix this issue.
We will most likely consolidate the affected prefs (lightning-main-in-composite, lightning-main-default) when migrating the calendar registration to moz prefs (bug 378754). I know this makes it hardly better, but we should at least remove those prefs properly.
Assignee: daniel.boelzle → nobody
Just another data point, identical thing happened to me.
I vote to close this bug with WONTFIX. As Stefan noted, 0.7 is already out, so we can't create any migration code to reselect the calendars. What we could do is do this for 0.5 -> 0.8, but I really don't see why this should be done, as its not so hard to reselect the calendars and we are still pre-1.0
It's not hard to reselect but I didn't figure it out and was about to file a bug report and I ran across this.  Maybe not everyone has updated, or maybe put it in release notes, who knows.  But there are people I know who would just say, "Eh, skip it" and find another calendar.
This is already in the release notes.
Status: NEW → RESOLVED
Closed: 17 years ago
Keywords: relnote
Resolution: --- → WONTFIX
This will be fixed in 0.8. See bug 413128.
Keywords: relnote
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.