You would still be able to use the new Firefox with this setup.Īnother option (if you are sure you do not want to use the new, non-ESR Firefox anymore) would be to delete the new profile that was just created and rename the profile you want to use to the same name as the folder you just deleted. As you add to one or the other, they will (of course) diverge over time. That way will have two profiles that have different names and are associated with different Firefox versions, but are otherwise identical, for now at least. That way, it will pick up your history, saved logins, addons, custom stylesheets (if any), and everything else in your profile, as well as the prefs. Then delete compatibility.ini inside that folder, and you should be good to go. You can then copy everything from the profile folder that you’ve been using (the good one that you want to migrate to ESR) into the folder that was just created (it will have a creation date/time that reflects when you first ran ESR), overwriting everything that’s already in there. Once you are there in the File Manager, close Firefox. Just go to the root folder of whatever profile it has as the default, and when it opens the File Manager, just go up one level to get to the Profiles folder. You can use about:profiles in the URL bar to get quickly to the profile folder location. With newer versions, it just does it and tells you what it did. It will give a message saying that it has to create a new profile to prevent problems… when I tested 78 ESR just now, it gave an option to create new folder or exit. I would run the ESR version of Firefox (make sure the non-ESR version is not in use first!) to let it create its new profile folder.
They evidently were not important, but as long as I was in there (prefs.js), I went ahead and fixed it.
#FIREFOX 78 ESR WINDOWS#
I just edited out some of the Windows paths just a few weeks ago. I copied it to Linux, then to the other Linux PCs, and so on, and it’s still the same one. I’m still using the same Firefox profile I used years ago in Windows, FWIW. You could probably also replace the actual new profile folder with a symlink to the one you want it to use, then delete compatibility.ini. The actual new profile folder that was created can be deleted.Īfter that, Firefox should use the old profile without any issues.
I also remove compatibility.ini within the profile itself. In order to reassure Firefox that all is ok and that it’s ok to load the profile, I just replace the name of the new profile folder that was created with that of the profile I want it to use, in both installs.ini and profiles.ini. Each Firefox installation gets its own installation ID, and it will create a new profile if the existing profile is associated with a different installation ID.Īs always, be sure to have backups before messing with profile folders. The updates are also available for direct download.I installed the ESR version about a week or so ago to test its performance, and I used my old (v81) profile without any problems, once I overcame Firefox’s aggressive disobedience as far as just loading the dang thing.įirefox has become very annoying with its creation of new profiles even if the new Firefox installation is the same version as the old one. The release notes indicate a bug fix: Fixed that old preferences were not applied correctly when set via GPO.įirefox 81.0.1 and 78.3.1 can be downloaded from this website (the variant can be selected from the list boxes displayed).
#FIREFOX 78 ESR UPDATE#
There was also an update of Firefox 78.31 esr with one year long term support. The developers have also fixed various stability problems. Fixed high memory growth with addons such as Disconnect installed, causing browser responsiveness issues over time (bug 1658571).Fixed Picture-in-Picture controls being visible on audio-only page elements (bug 1666775).Fixed legacy preferences not being properly applied when set via GPO (bug 1666836).Resolved incorrect scaling of Flash content on HiDPI macOS systems (bug 1667267).Fixed missing content on Blackboard course listings (bug 1665447).The release notes for version 81.0.1 lists the following fixes:
0 kommentar(er)
