Thanks for noticing this. This is an issue in the core code, a section that does not correctly support custom filters. I will need to fix it in the core code, as fixing it in the extension would require a very tacky overwriting of a core js function. I opened a bug for this, https://bugzilla.mozilla.org/show_bug.cgi?id=549336
I believe that this code is only used in views though – but would affect any custom search term, not just the ones you mentioned.
Could you try some other ways of accessing this, to confirm that in your case? That is, I think the custom term should work in either virtual folders, or in advanced search (select the folder, right click, "Search").
I'm going to have to investigate this further. You say it only appears in "some folders". Can you tell me how those folders might be different from those that do not show this error?
I have made some test.
My mailbox is IMAP one. It works on some folders with few messages inside. I have made some additional test and copy whole inbox to "test" folder inside Local Folders and then apply my custom filters (with regexp) to this "test" folder -> it works. But on inbox inside IMAP mailbox -> error. Rebuild index doesn't help.
One more test, after switching to Offline mode -> no error,
it works.
I didn't think that advanced search used searchSpec.js, but it must if you are getting that message. I really need to fix that in core, and I'll try to get to it soon.
Login 
Register 
Home
Reply to Post
Add a New Topic
Quote and Reply 
Topic RSS 
Recent Comments