I would like some clarification on the best procedure to update Firefox Portable.
Obviously, the easiest way to do it is through the app's update feature. However, while the forum FAQ says that's fine, the support FAQ says that it may leave some extraneous data behind, and some of the forum posts say it will screw up Add-ons/Extensions.
What is the correct answer as to how using the internal update feature will affect things?
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
It's best to just use the app updater built into the current 2.0 Beta release as it's just two clicks. Second best is to download the new version and do an 'in place upgrade', just installing it over the old one. The reason is that that way you get any new features or bug fixes made to the PA.c Launcher. In the latest release, for instance, I added in portablization of the plugin registry so you could set plugins as disabled and keep them installed in Firefox Portable.
Last would be Firefox's built in updater, which will update just Firefox itself (not the Firefox Portable launcher). It should work fine and it will, at most, leave a single empty sub-directory behind on the local PC.
Sometimes, the impossible can become possible, if you're awesome!
Thank you for clarifying that for me. I don't use the launcher, so that's out. But I wasn't aware (or had forgotten) that there were other components that wouldn't get updated by Firefox's built in updater.
I was able to get the in place upgrade to work, after figuring out the small bug regarding folder names.
Thanks for helping!
>I don't use the launcher, so that's out.
Otto Sykora
Basel, Switzerland
I think by launcher, Kernel means the Portable Apps Menu.
That is correct. Sorry about the confusion!
It's in the profile folder, which is portable. So it seems to me that the plugin registry should therefore be portable. So... why isn't it?
"Insanity is doing the same thing over and over and expecting different results." - Albert Einstein
My use of Google indicates that I am insane.
Plugins are portable... in that you can carry them around with you (though their settings are not portable if they have any e.g. flash cookies, etc). The plugin registry is where FF keeps track of what plugins you have disabled previously. This did not used to be portable because the paths weren't updated. They are in the new release.
Sometimes, the impossible can become possible, if you're awesome!