Cannot uninstall 0.9rc1 and reinstall 0.8 due to compatibility conflict



10 years ago
10 years ago


(Reporter: toto_vich, Unassigned)





10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2008070208 Firefox/3.0.1
Build Identifier: 0.9rc1

I installed Lightning 0.9rc1, had issues related to timezones and wanted to return to Lightning 0.8.
I deleted all calendars from the GUI (had one local) and uninstalled 0.9rc1. When I (re-)installed 0.8 I got an error that a newer version of the add on had been used and to keep me from corrupting data I was prevented to enable 0.8.
I tried deleting everything from the extension directory but that didn't help either. 

Reproducible: Always

Steps to Reproduce:
1. Install 0.9rc1 + restart Thunderbird
2. Uninstall 0.9rc1 + restart Thunderbird
3. Install 0.8 + restart Thunderbird
Actual Results:  
Can't enable 0.8

Expected Results:  
Enable 0.8 possibly with the need to reimport the calendar data
What means 'issues related to timezones'? Did you filed a bug for this?

Downgrading the calendar database is not supported. The current behavior is as specified.

Comment 2

10 years ago
1. Eventually I managed to reinstall the 0.8 addon by deleting the storage.sdb file. However, it would be nice if this could be added as a feature for downgrade (at least beginning from 0.9). Give the user the option to delete the data in the new format but don't lock out the older addon version... (luckily I created a backup of my calendar before upgrading so I just wanted to downgrade to a clean calendar which I could import the old data back into).

2. timezone issue - I am not sure if this is a Lightning issue of a ScheduleWorld issue. I just noticed that after syncing all of my appointments moved by one hour and apparently kept on moving thereafter. I posted about this on the ScheduleWorld forum (not sure who is to blame...).
Resolving INVALID, but you can file an bug regarding an enhancement for downgrade for comment#2 (1.).
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.