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.
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.