Execption cookies dont stay saves when I log off then on
after installing win 10, I cant save the exception cookies or allowed popup sites when I log back in all saved sites are gone. If I cant fix this I will have to start using another browser (I reinstalled foxfire, That didnt help!)
Mike
Wybrane rozwiązanie
Hi Mike, don't panic, it's do-able.
Do you have Firefox set to clear your history when it closes? Make sure you are not clearing the following categories:
- Cookies
- Site Preferences
The way to clear unwanted cookies at shutdown is to accept them either (i) only for the session or (ii) not at all. Use the "Keep until: I close Firefox" setting to limit cookies to session only, and create "Allow" exceptions for sites you permit to create persistent cookies.
Please see the attached screenshots.
Also, if you need to manage a lot of cookie permissions, there are some extensions to ease the pain of using the various dialogs.
Przeczytaj tę odpowiedź w całym kontekście 👍 0Wszystkie odpowiedzi (4)
Wybrane rozwiązanie
Hi Mike, don't panic, it's do-able.
Do you have Firefox set to clear your history when it closes? Make sure you are not clearing the following categories:
- Cookies
- Site Preferences
The way to clear unwanted cookies at shutdown is to accept them either (i) only for the session or (ii) not at all. Use the "Keep until: I close Firefox" setting to limit cookies to session only, and create "Allow" exceptions for sites you permit to create persistent cookies.
Please see the attached screenshots.
Also, if you need to manage a lot of cookie permissions, there are some extensions to ease the pain of using the various dialogs.
I know all that: Allowed exceptions for sites & popup rules that I save don't stay saved after I installed win 10!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOT EXCEPTIONS STAY SAVED WHEN I EXIT FOXFIRE.
If I can't fix this by tonight I will remove Mozilla from my computer.
Check this article for possible reason that Firefox isn't recording changes to disk, or those changes might be getting cleared by another process: