There seems to be a bug in the FFP launcher. If the license page is shown and the profile directory is empty, the launcher will ask twice if you want to create a profile. Once before the license agreement is shown, and once after you agree to it.
By the way, this same bug exists in the TBP launcher.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
That's an odd situation, since it shouldn't really happen that way (there should never be a situation where it's pointing to a directory with no profile). I'm actually going to be removing that warning from a later release and just let FF create one from scratch in that instance.
As I recall, you're using a non-standard layout (not FFP directory with the App and Data directories and then the appropriate subdirectories). These non-standard layouts aren't really tested for in the newer releases.
Sometimes, the impossible can become possible, if you're awesome!
Correct. Still, even when I installed the newest FFP and ran it with the standard directory structure (before moving the directories around and adding an INI), I got the warning. Not sure why.
But yeah, Firefox will happily create a default profile if pointed at an empty directory. Same goes for Thunderbird. Therefore, there's really no point in having a warning message. Removing it is probably the best option.
-
< ExplosivePrincess 2.0 Atomic Bomb Edition >
warning: keep explosiveprincess away from children
A standard install doesn't display any warning at all if you don't mess with the files in App or Data. I just verified it by DLing a fresh copy, extracting and running. No warnings, as expected.
The profile warning was more there for some folks messing with the INI and pointing it to the wrong directory by accident. FF and TB will create default profiles... but with the default options like cache enabled, which results in a pretty bad user experience.
Sometimes, the impossible can become possible, if you're awesome!
Does it make any difference that in the aforementioned "standard install", I first moved FirefoxPortable.exe to the directory immediately above FirefoxPortable, as opposed to inside it? I'm thinking that may have been the issue.
-
"You missed the bigger picture, Bruce. You always have."
- Robert Spellbinder, Spectacles: Bruce's Story
It doesn't work the the DefaultData profile, which only works in a standard layout... so FF creates its own profile, hence the warning.
Sometimes, the impossible can become possible, if you're awesome!
Still, I shouldn't get a warning with that configuration as it's one of the "officially supported" layouts (i.e. supported without an INI).
-
"You missed the bigger picture, Bruce. You always have."
- Robert Spellbinder, Spectacles: Bruce's Story
I'll drop the alternate launcher location and the warning error from the launcher in the next release and add a note to the readme.txt that if you change the location of the files with the INI without running it once, you'll get a default profile instead of the special portable one. (If you're manually moving stuff around already, manually copying in the 'default' profile... or your current local one and adjusting it... isn't a big deal.) The alt launcher location isn't supported in several of the new apps anyway, so dropping it will make the older apps like FF consistent with the newer ones.
Sometimes, the impossible can become possible, if you're awesome!