Dropping from Beta to release channel
I am stuck between two machines and can't stay on beta updates anymore because FF won't let me sync my profiles anymore.
If I can't migrate my beta channel profile to the release channel, how can I quit beta updates until the release channel catches up to me?
FF preference selected is 'download updates but let me install them' but really there is no choice. It installs and next opening of FF it is automatically installed. I already changed about:config preference for update channel to 'release' but FF merrily kept on with beta channel updates.
I need my beta channel profile customizations--varied management of permissions and add-ons and passwords on dozens of sites, customizations to stop the blinking and autoplay and movement and noise.
But: FF won't let me keep them if I go back to release.
So: how can I force FF to stop updating while the release channel catches up?
Mac/Mojave Beta channel 80.something, need to sync with release channel 79
選ばれた解決策
You can uninstall the beta version if you do not want to use this version and install the current Firefox release and let it create a new default profile.
Make sure not to remove your beta profile folder.
You can copy specific files with Firefox closed to the current profile folder to recover personal data.
- bookmarks and history: places.sqlite
- favicons: favicons.sqlite
- bookmark backups: compressed .jsonlz4 JSON backups in the bookmarkbackups folder
- cookies.sqlite for the Cookies
- formhistory.sqlite for saved autocomplete Form Data
- logins.json (passwords) and key4.db (58+) or key3.db (57 and older) (decryption key) for Passwords saved in the Password Manager
if you only have key3.db then make sure to remove an existing key4.db - cert9.db (58+) or cert8.db (57 and older) for (intermediate) certificates stored in the Certificate Manager
if you only have cert8.db then make sure to remove an existing cert9.db - persdict.dat for words you added to the spelling checker dictionary
- permissions.sqlite for Permissions and possibly content-prefs.sqlite for other website specific data (Site Preferences)
- sessionstore.jsonlz4 for open tabs and pinned tabs (see also the sessionstore-backups folder)
すべての返信 (5)
The app.update.channel preference in about:config just basically shows what channel you are on as modifying it in about:config has no impact. The app.update.channel has not been a modifiable preference since Firefox 4.0
You have to either edit channel-prefs.js file or just download and install a build on the channel you want. The editing of file will only work in going from say Beta to Nightly and not other way.
この投稿は James により に変更されました
Thank you!
I do not see channel-prefs.js in Application Support > Firefox, nor does Finder.
Might it be under a different name?
選ばれた解決策
You can uninstall the beta version if you do not want to use this version and install the current Firefox release and let it create a new default profile.
Make sure not to remove your beta profile folder.
You can copy specific files with Firefox closed to the current profile folder to recover personal data.
- bookmarks and history: places.sqlite
- favicons: favicons.sqlite
- bookmark backups: compressed .jsonlz4 JSON backups in the bookmarkbackups folder
- cookies.sqlite for the Cookies
- formhistory.sqlite for saved autocomplete Form Data
- logins.json (passwords) and key4.db (58+) or key3.db (57 and older) (decryption key) for Passwords saved in the Password Manager
if you only have key3.db then make sure to remove an existing key4.db - cert9.db (58+) or cert8.db (57 and older) for (intermediate) certificates stored in the Certificate Manager
if you only have cert8.db then make sure to remove an existing cert9.db - persdict.dat for words you added to the spelling checker dictionary
- permissions.sqlite for Permissions and possibly content-prefs.sqlite for other website specific data (Site Preferences)
- sessionstore.jsonlz4 for open tabs and pinned tabs (see also the sessionstore-backups folder)
Thank you!
I received permission to update my Enterprise version of Firefox that was stuck at version 68 (!) and replace it with current firefox release....so version 79 is happy with version 79. Yay!
Note that if you are on the ESR update channel it is quite normal to stay at Firefox 68 ESR (current is 68.11.0) and receive only security updates.
Firefox 68 ESR is about to be replaced by Firefox 78 ESR.