InformAction Forums

You were right, and I'll take my pie a la mode. It's bug 587088 and at least one other NoScript user posted, it looks like for the same update that caught me. Here's the developer's theory: The process for installing an update is to first delete the files from the old version, then move the new file...

There's no point in keeping it in this state, unless you're willing to file a bug at https://bugzilla.mozilla.org, since it may be an Add-ons manager bug (definitely not a NoScript one). Hmmm ... "definitely" is a bold word to use about anything technical, but hopefully that's it. If Mozi...

I'm not sure how to submit bug reports, but this seems to be the place. Given it's nature, it's hard to reproduce, but I've got some pretty good info. Rather than repeat myself, see here:

http://forums.informaction.com/viewtopi ... 97&p=22137

I'll leave my browser in it's current, NoScript-less state for a day or so, in case someone wants to troubleshoot, but then I'm going to reinstall. I don't like to have random encounters with websites without protection.

I think a failed NoScript update on Firefox 4.0 beta 6 (on Win7 x64) caused NoScript to be uninstalled. I'm an experienced IT professional and know my way around computers. I didn't quite witness it happen, but here is what I can tell you: 1) Yesterday, NoScript was installed and working 2) Yesterda...