![]() ![]() While Waterfox is an example of that kind of program it still creates the profile data outside of the main installation directory, so isn't truly what people would consider portable. So, if it is Windows opening Waterfox rather than you (because it was made the standard browser, otherwise it would have opened Edge - or Internet Explorer, before Windows 10) it should be no different. But AFAIK if you click directly on the executable rather than on the launcher, it does not automatically or logically follow that Waterfox will not find its profile folder anymore. I have been using them for as long as they exist, for about 10 years or more I think, so this is not news to me. Yes, this is how PortableApps portable applications work and always did. Well yes I was supposing it because I had a brief look at the portable app version and saw there were two executables, so I came to what I thought was a logical conclusion. ![]() It was after it had restarted that I got the message, but I am not sure why Windows tried to open Waterfox at that point. I did a Windows Defender offline scan which will automatically restart your computer. I remember now what it was I was doing before getting that message (I had forgotten because there were several things I did recently with Windows, amongst which using the anti-ransomware settings). Why is there a separate folder with profile data in the AppData directory? As this is a portable app it should be self-contained and not have installed anything on the computer. So I thought it made sense to just check "don't import anything". Secondly, it was mentioning importing "existing Waterfox data" but the only options it gave was importing either from MS Edge, or from Internet Explorer. Sure enough, on checking I found in the AppData/Roaming/Waterfox directory, there was a folder with profile data. It was not clear what it meant, as Waterfox Portable always had its "own profile location", just like any other Portable App. If you are coming from an older version of Waterfox, you will need to import your existing Waterfox data as previously this data was shared with your Firefox profile.įirstly, this "own profile location". Waterfox now uses its own profile location to store your personal data. No options are greyed out in the legacy version.Today, Windows wanted to open Waterfox (I had made Waterfox my standard browser earlier) but it opened a Waterfox browser window I had never seen before (grey on top and without any addons - at first I thought this was Edge) and showed this message from the Waterfox Wizard: To avoid all this rigamarole, use the latest "legacy" version, 1.16.4.11, and install uBO Updater, which forces the browser to look for uBO updates at GitHub, and to only look for the latest 1.16.4.nn version. Are you really that determined to run 1.18.16? One more thing: Serpent 55 is different! Because it identifies as FF 55, you don't need to edit the minimum version, and AMO will offer 1.18.nn, but it will also offer newer versions that won't run! You can get around that by downloading and installing 1.18.16, then spoofing Serpent's version number as 5 3 so AMO won't keep offering incompatible "upgrades."įinally, after all that, you'll find that a few uBO options are greyed out. (BTW, it's possible to install an unsigned extension in non-ESR FF builds too, but it's trickier: you have to set up some JavaScript to run at browser startup.)Įdit: BNavigator is UXP-based too, so the uBO 1.18.16 should work there also, after the usual "surgery" required to install anything on that browser (including removing the signature). That's the default in builds, so you don't have to worry about that with his builds. In FF 52 ESR, you then have to set to false to install it. This will invalidate the signature, so you should remove that too, making it an unsigned extension. Next, you need to edit the minimum version requirement down from 55 to the FF/Serpent version you're running. It's probably simpler to get uBO from GitHub instead. ![]() Then you have to click "See all versions" and scroll down to 1.18.16 (newer versions won't run). It still runs OK on older versions, but to get it from AMO, you must spoof your FF version number to 55 in the URL (at and ) and user agent (at .), or AMO won't offer anything past 1.17.4. Well, there may be a bit of a problem: Gorhill upped the minimum required version to 55 in 1.18: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |