wangvisual
caught exception type error: msgFolder is null
Can't get addon to work except with single folders. I get the following errors;
Warning: attempting to write 6764 bytes to preference extensions.exchangecalendar@extensions.1st-setup.nl.82ebeba7-9fb6-4092-8c92-47446f8964d9.syncState. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. This preference will not be sent to any content processes. Caught Exception TypeError: msgFolder is null updateFolderStyle@chrome://awsomeautoarchive/content/autoArchivePrefDialog.jsm:103:1 initFolderPick@chrome://awsomeautoarchive/content/autoArchivePrefDialog.jsm:147:5 creatOneRule@chrome://awsomeautoarchive/content/autoArchivePrefDialog.jsm:271:7 createRulesBasedOnString/<@chrome://awsomeautoarchive/content/autoArchivePrefDialog.jsm:375:9 createRulesBasedOnString@chrome://awsomeautoarchive/content/autoArchivePrefDialog.jsm:374:7 syncFromPerf@chrome://awsomeautoarchive/content/autoArchivePrefDialog.jsm:388:5 anonymous@chrome://messenger/content/preferences/preferences.xml line 440 > Function:3:8 setElementValue@chrome://messenger/content/preferences/preferences.xml:442:20 updateElements@chrome://messenger/content/preferences/preferences.xml:562:13 _constructAfterChildren@chrome://messenger/content/preferences/preferences.xml:31:9 preference_XBL_Constructor@chrome://messenger/content/preferences/preferences.xml:169:11 openOption@chrome://awsomeautoarchive/content/autoArchive.jsm:184:5 createPopup/<@chrome://awsomeautoarchive/content/autoArchive.jsm:231:82 autoArchivePrefDialog.jsm:103:1 Warning: attempting to write 6760 bytes to preference extensions.exchangecalendar@extensions.1st-setup.nl.82ebeba7-9fb6-4092-8c92-47446f8964d9.syncState. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. This preference will not be sent to any content processes. Webconsole context has changed Warning: attempting to write 6764 bytes to preference extensions.exchangecalendar@extensions.1st-setup.nl.82ebeba7-9fb6-4092-8c92-47446f8964d9.syncState. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. This preference will not be sent to any content processes. Warning: attempting to write 6760 bytes to preference extensions.exchangecalendar@extensions.1st-setup.nl.82ebeba7-9fb6-4092-8c92-47446f8964d9.syncState. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. This preference will not be sent to any content processes. uncaught exception: 2147746065 autosync.js:206:13 uncaught exception: 2147746065 autosync.js:206:13 uncaught exception: 2147746065 autosync.js:206:13 Warning: attempting to write 6764 bytes to preference extensions.exchangecalendar@extensions.1st-setup.nl.82ebeba7-9fb6-4092-8c92-47446f8964d9.syncState. This is bad for general performance and memory usage. Such an amount of data should rather be written to an external file. This preference will not be sent to any content processes.
I'm grateful for every fix you guys are providing .. what confuses me though is that there is no version numbering for identifiying the latest build. Just feedback .. I'll manage ;-)
Working on TB 68.11.0 for Mac Mojave 10.14.6. I uninstalled Expression Search, installed the new version, restarted TB. Thank you!
Great! I were going to do the same! Thanks for your work @fp66 , I just downloaded and works fine. I think next time we should update the json up version 99999, and wait until doesn't works anymore......
How can we request this feature be available as native filter on thunberdird? Realy, standard filter system sucks....
I actually disabled t-bird updates after 68.10...at least this way I choose when to have the "battle for expression search".
You might want to set "strict_max_version" to a higher value than "68.11.0" or else you'll need to manually fix it with every update.
For the others: just edit the manifest.json in extension's folder (inside your TB's profile), you can set something like "69.99.0"
I did it, I modified "strict_max_version" in the manifest to "69.99.0", but it stopped working... The extension installs and is recognized in TB 68.11.0, but it stops working with this simple change...
Does anyone have clue why this does not work...
The best solution will be a native TB support, please add your vote here https://bugzilla.mozilla.org/show_bug.cgi?id=538821
I changed "strict_max_version" to 68.12.0 - but this simple change doesn't allow to re-install the add-on once again. :-(
