Bugzilla@Mozdev – Bug 24452
Thunderbird 3.1.11 forgets settings in new Quickfolders version
Last modified: 2011-09-30 05:57:26
You need to log in before you can comment on or make changes to this bug.
I've installed the new Quickfolders on Thunderbird 3.1.11 running on 64-bit Linux Mint 11. Not only did it wipe the existing folders that I had set up, but although I can drag folders to the Quickfolders bar when Thunderbird is running, they are all forgotten and the bar is emptied every time I shut the program down and restart it. Hope you can help. Jon.
(In reply to comment #0) > I've installed the new Quickfolders on Thunderbird 3.1.11 running on 64-bit > Linux Mint 11. Not only did it wipe the existing folders that I had set up, but > although I can drag folders to the Quickfolders bar when Thunderbird is > running, they are all forgotten and the bar is emptied every time I shut the > program down and restart it. Same problem on TB 3.1.10, openSUSE 11.2, i686. The QF Toolbar also returns after removing it and restarting TB. Seems that the entire config goes poof whenever 2.9 starts. (Sidenote: "Read Version History" link in the options' "Support" tab doesn't work, either. It's the only one including a leading "http://" ... ?) Probably a dup of bug 24451, though.
(Why isn't 2.9 listed in the version history, anyway ... !?)
I can confirm this behavior: just updated from Quickfolders 2.8 to 2.9 on TB 3.1.15 running on a XP 32-bit machine and my previous settings are gone. Also dragging new folders to the bar and restarting TB result again in an empty bar :-( - Taminon
URGENT INFORMATION FOR AFFECTED USERS: Do *NOT* try to manually rebuild your folders when you "lost" them. The QuickFolders.folders configuration, which contains your folder settings, apparently *DOES* survive upgrade+restart, but is rewritten as soon as you modify the "empty" folder pane. (Too late for me, alas. :-/ ) Boldprint in the extended config claims that there are *more* nondefault configs (assumedly survivors of the wipe). Will attach screenshots.
*** This bug has been marked as a duplicate of bug 24451 ***