[UNRELATED] Lost settings

[nottledim]

I think it must have been the the update to 2.5.9 but suddenly my NoScript settings have been changed. Two things specifically caught my eye: under General "Temporarily allow top level sites by default" it's now unticked. Secondly my ABE rules have been reset (aka lost).

Doing a diff on today's prefs.js and that from 2 days ago shows many differences for noscript including what looks like all my temp whitelists, my ABE settings and loads more.

ABE.rulesets.
clearclick exceptions
temp
untrusted

Have all been reset

This has happened on two systems both Debian GNU/Linux testing iceweasel 16.

Is there an explanation for this? Should I just patch prefs.js back to how it used to be?

Thanks

[Thrawn]

Sounds like you're right, things have been reset. No idea why, but yes, I'd recommend patching prefs.js.

You haven't, by any chance, created a new profile? If you had, that would explain it. Not something you could do accidentally, though.

[nottledim]

You haven't, by any chance, created a new profile? If you had, that would explain it. Not something you could do accidentally, though.

No, definitely not. This has happened on two systems so I don't think it's finger trouble.

Dick

[Tom T.]

Both are Iceweasel? Please note that NoScript is always intended to be compatible with Firefox and SeaMonkey, and while it works with many other Mozilla-based browsers, these forks may at times have changes which could affect NS. The update did not change any of my settings on Fx 16.0.2.

Far easier than accidentally creating a new profile would be accidentally clicking the "reset" button in NoScript Options.
I realize that this is less likely to have happened on two occasions, but the word "testing" caught my eye. Try a fresh install of Firefox or SeaMonkey on the same systems. If they don't have this problem, it may be something to talk about with the Iceweasel people.

many differences for noscript including what looks like all my temp whitelists

Temporary whitelists are exactly that -- temporary. The permissions are revoked when you close the browser (if you don't manually revoke them first), so you would not find an entry in prefs.js.

For what it's worth, I frequently back up my profile(s) to a flash drive. You can drag 'n drop, or I use a simple batch script. Doesn't solve the issue of what's causing this, but it does make it easy to restore the entire profile, not just prefs.js. (Also makes synching easy without using Firefox Sync, but that's getting O/T.)

[nottledim]

Both are Iceweasel? Please note that NoScript is always intended to be compatible with Firefox and SeaMonkey, and while it works with many other Mozilla-based browsers, these forks may at times have changes which could affect NS. The update did not change any of my settings on Fx 16.0.2.

Far easier than accidentally creating a new profile would be accidentally clicking

No, there was no accident (finger trouble) but I did notice something yesterday which I passed over but which popped into my head overnight. That's Sync. What I'm guessing has happened is that Sync has synced my lesser used laptop first and put its prefs settings on my desktop. Having restored my desktop config last night I notice that sync has now updated my laptop with the desktop settings .

So there ... something to watch out for. It may well nip somebody else.

Thanks for your help

Dick

[Tom T.]

... What I'm guessing has happened is that Sync has synced my lesser used laptop first and put its prefs settings on my desktop. Having restored my desktop config last night I notice that sync has now updated my laptop with the desktop settings .

So there ... something to watch out for. It may well nip somebody else.

Which is exactly why this writer personally prefers to use batch scripts or other backup-and-sync methods vs. Firefox Sync. IMHO. YMMV.

Thanks for reporting back. Will mark appropriately.