Copy shortcut from Start Menu, paste on desktop, and r. clk and hit Properties, and (if running Windows 64 bit) change to "C:\Program Files\Mozilla Firefox\firefox.exe" -no-remote -p
If you are running Windows 32 bit use C:\Program Files (x86)
In Linux Ubuntu, Firefox program should be in /usr/lib/firefox
Profile should be in /home/username/mozilla/firefox (put your user name where it says username)
To add another profile, drag icon from Applications launcher (Start Menu,) to Desktop, r. clk and hit Launcher and change to firefox %u --Profilemanager and click close. Then launch and choose Create new profile.
Migration
Most important files to migrate are
cert8.db
formhistory.sqlite
key3.db
persdict.dat
places.sqlite
signons.sqlite
I have not had Firefox after what Mozilla did to Brandon Eich.
I’m running Mozilla 61.0.1 (64-bit) for Linux Mint. It’s about a damned mess. I’m not crazy about Chrome, but it is a better browser.
I stopped it updating at 53.0.3 & have retained all my add ons.
Primarily I wanted to keep FIRE FTP, which is a simple and easy FTP client that is integrated into Firefox.
That & accessing Easynews is all I use Firefox for anymore.
LOSE....not Loose!
Anyway, back to the program.
Just another reason to hate this house and the process of selling it. :mad:
I still use FF ER 52. It retains most of the older extensions.
With FF 57, many of the old extensions quit working. Their new versions, if any, just do not work like the old classics. Many programmers quit updating their apps a long time ago due to FF/Mozilla’s rapid release.
I keep trying to fend off updates and the need to upgrade. However, many websites demand browser upgrades.
==
To retain old upgrades and stop them from updating, so to FF Tools >> Add-ons or CTRL+SHIFT+A
Select the pull-down at the Settings Icon [top of add-ons page]
Uncheck ‘check for updates’
I’m running Firefox 61.0.2. I didn’t notice any change when it went from 59 to 60, but then I use a web browser for the content, not as a sandbox to make all kinds of pretty sand castles in.
Firefox ESR updated to Quantum (Remaining FF legacy add-ons broken).
Have never used any of the addons that you are concerned with, so updateing to 61.02 64bit has not affected my use of Firefox.
And to the FF 61.02 64bit I have installed the addon “Gostery” which can block all trackers, and does, unless I go to Gostery and unblcok something it has blocked.
Performance wise the biggest change with FF Quantum is it moved some of the performance processes from the FF “conversation” (back and forth in the Internet transmission) to multiple executables of FF running in the processor of the computer as individual and distinct “processes”.
With my pc’s AMD A4-3420 2.8 Ghz processor with 4gig of ram FF 61.02 has had events where it really slowed down, compared to the same Internet experiences under the last non-Quantum version of FF.
I think there must be something only tech elitists consider as “better performance” when it comes to FF Quantum. My actual FF peformance experience has been generally no different than before Quantum, with a few occassions of FF, with all its individual processes working in the CPU’s ram, litterally “bogged down”, even though Task Manager does not register the event as FF “not responding”. That is rare, so I have not gone back to pre-Quantum FF.
.. >> Warning (if you use Firefox esr) do not update to Firefox 60 unless...
daniel, much easier said than done - if not impossible. since yesterday FIREFOX59esr updates to QUANTUM, whatever your no-updates-settings are.
have also tried entries in about config (( app.update.auto - false app.update.enabled - false app.update.silent - false )) - they do stick, but FF59 updates anyhow.
any suggestions, any ideas?
greets - henry
I just opened up Chrome and now it looks totally different.
You will need the original .xpi file used to install the extension. I keep all versions I've ever installed.
Change the file name from extension.xpi to extension.zip. Then unzip the file to its own directory. Once done, edit the "install.rdf" file. It is a text file. Look for fields that state:
<em:minVersion> 38.0</em:minVersion>
<em:maxVersion> 55.0a1</em:maxVersion>
Make sure your version number of FF falls between the two version levels.
Once changed, save the file, then zip up the contents of the directory, then change the extension install file name back to .xpi and re-install the extension.
Caveat, most times it works but sometimes the extension will exhibit funky behavior or not work at all. But it's worth a shot.