-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception TypeError: msgFolder is null when opening Add-on #114
Comments
Same as above but Win 7: NS_ERROR_FAILURE: Couldn't decrypt string crypto-SDR.js:179 |
I guess I've the same here on Windows 10 / TB 60.6.0 (the add-ons is currently not usable/not working):
|
I can confirm @jkavery finding for Thunderbird 60.5.1 (Linux, 64 bit). The drop-down box for the
|
Same here on Windows 10 / TB 60.6.1 (the add-on is currently not usable) Caught Exception TypeError: msgFolder is null row is undefined autoArchivePrefDialog.jsm:287 |
Also occuring on Windows 7 TB 60.6.1. Have 4 IMAP accounts (3 external internet and one internal intranet). After the message, am unable to configure archiving as destination folder dropdown is not populated. Add-on is not usable. Caught Exception TypeError: msgFolder is null |
is this project still maintained? |
To work around the problem of there not being a Destination Folder drop-down when adding a new rule, add one or more new rules, filling in everything except the Destination Folder(s). Then quit and restart Thunderbird and edit the options again. The Destination Folder(s) of the new rules will now have drop-downs which can be used. |
I loaded this app specifically to use the Archive function -- and to AVOID having to set a destination folder. Using the Archive button in TB automatically selects a folder for you, based on the current yet. This display bug, while annoying, doesn't seem to affect the functionality. It's just a reminder that the logic for checking Archive parameters needs to be cleaned up. |
This matches my experience. |
When opening Awesome Auto Archive 0.8 to configure it for the first time, Thunderbird 60.5.1 (Linux) reported these exceptions:
The text was updated successfully, but these errors were encountered: