InformAction Forums

Hello,

I've encountered problems using Zotero (http://zotero.org) and NoScript at the same time: As long as NoScript is active, I'm unable to edit notes in Zotero, which uses TinyMCE internally. Instead Zotero displays a message that I should add "file://" to my NoScript whitelist. I've done that, but it didn't help. I've asked in the Zotero Forums and got some responses about how I should add "file://" or "file:" to my NoScript whitelist. To cut a long story short: It didn't work. (For details see http://forums.zotero.org/discussion/147 ... er/#Item_7.)

I'm currently running Iceweasel 3.0.6 (the version included in Debian Lenny), NoScript 2.0.3.5 and Zotero 2.0.9 on a clean and fresh profile. Disabling the NoScript plugin fixes the problem and so does "Allow Scripts Globally", but this is not a permanent solution for me...

My question is now: Is there a way to generate some debug output to see what exactly was blocked by NoScript? The debug option of Zotero didn't generate any useful output and the Firefox Error Console doesn't show anything useful either. My search in these forums, the NoScript homepage and the internet in general was not yet successful.

I'll be glad to supply further details if necessary.

Greetings,
Arnd

Either adding "file:" or "file://" did work for me, but only ON NEW WINDOWS, i.e. I had either to spawn a new window from the File menu or restart the browser in order to have the notes editable in the Zotero panel after changing the permissions (probably because the file:// scripts are loaded at window startup time).

If this doesn't work for you, please try /NoScript Options|Reset/, then adding back file:// to your whitelist (which got reset).

I got exactly the same suggestion in the Zotero Forum. I've tried creating new windows and restarting the browser after each operation I tried. I also did a NoScript reset and added file: and file:// via different ways (and of course restarting Firefox), which didn't change anything.

So far I've tried the following methods:
- Adding "file:"
- Adding "file://"
- Adding both

via:
- the NoScript options dialog
- browsing to file:/// and using the context menu
- exporting the whitelist, clearing it, then editing the exported file and reimporting it
- reseting NoScript and adding it via the options dialog

Afterwards I always restarted Firefox.

None of this worked. Therefore I wanted to ask if there is some debug option so I can trace what exactly is going wrong.

arnd wrote:Therefore I wanted to ask if there is some debug option so I can trace what exactly is going wrong.

about:config, set noscript.consoleDump to 1 and noscript.consoleLog to true.
Warning: this can be very noisy and impact browsing performance.