Firefox 17 is not retaining cookie setting for websites. Besides removing all existing exceptions I had, it will no longer retain exceptions for cookies. I have the basic cookie setting as unchecked for accepting cookies (that is the default is not to accept cookies), but when I add an exception, it does not retain it when I close my browser. This is very serious stuff. I will have to move from my beloved Firefox to something that *does* work. I can't believe you haven't been flooded with complaints. Or maybe you have.
Try to delete the permissions.sqlite database file that stores the (cookie) exceptions.
You can use this button to go to the Firefox profile folder:
In case you are using "Clear history when Firefox closes":
Note that clearing "Site Preferences" clears all exceptions for cookies, images, pop-up windows, software installation, and passwords.
FWIW, I wrestled with this issue for a couple of hours and then downgraded to 16.0.1 at https://ftp.mozilla.org/pub/mozilla.org/firefox/re
I wish I had read your post earlier. I *didn't* have a backup for permissions.sqlite , or any other backup for Firefox. I followed the first bit of advise in this thread and reset Firefox, the result is that my whole browser was then destroyed. After nearly 10 yrs. of being loyal Firefox user I was not going to try and put Humpty-Dumpty back together again.
I appreciated Firefox wanting a secure browser but haven't we had three upgrades in the last 6 weeks addressing similar security issues? And releasing this latest update without testing for this issue was unbelievable....so sadly, after seeing my browser ruined, I uninstalled and moved to Chrome. When a person browses with the default of not accepting cookies and has a list of exceptions for the secure sites they need to visit this was a terrible glitch...and I would have "downgraded" but had no back-up to rely on as you did and when I saw what "troubleshooting" my browser did (left me with a ugly piece of nothing) I had no choice but to change my browser.
It is sad...but farewell Firefox friends...this was the straw that broke the camels back for me.
Firefox should be keeping permissions and exceptions if you aren't removing then by using clear history when Firefox closes to remove the site preferences.
If that isn't the case then you may have cleanup or security software preventing this or the permissions.sqlite file may be corrupted.
You can create a new profile as a test to check if your current profile is causing the problems.
See "Creating a profile":
If the new profile works then you can transfer some files from the old profile to that new profile, but be careful not to copy corrupted files.
@cor-el: should be keeping permissions and exceptions is definitely the operative phrase here. All I can say is that I used SQLite Manager to verify the integrity of my permissions.sqlite file, that 16.0.1 behaves correctly with this file, and that 17.0 fails to save and maintain certain permission exceptions with the same file. Reverting to 16.0.1 with the same permissions.sqlite restored expected behavior for me. I don't really have time to investigate or experiment further.
I'm with dzeleznik . Firefox is a tool for me, not a toy. I don't have any interest in dinking around with it to make it do what's it's supposed to be doing right out of the box. dzeleznik, thanks for the link.
Actually, I am very close to ditching FF entirely. It is increasingly common that I have to go to Chrome to see content that will not display on FF. And now this hassle. The main thing that keeps me is the fact that FF is not AFIK trying to spy on me as the others are.
When this frenetic release-of-the-week behavior started, I expected problems due to inadequate testing. The only surprise to me is that this is the first major regression that I have seen.
"Will avoid any upgrade beyond 16.0.1 until I hear the problem is solved. " Yes.