If I have an extension whose original XPI was not compatible with the current version of Firefox, but for whom there is a compatibility update available, this works just fine for the installed version of Firefox.
But for Firefox Portable, whenever I use it on a new machine, it seems that the compatibility update didn't travel with it, and I need to update extensions all over again.
Is there anything that can be done to fix this?
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
I am having this same problem. I am running Firefox Portable from a Dropbox share and every time I move to a new computer half my extensions fail to start.
jpe
If the relative path changes, compatibility updates may break. Is the path changing from F:\PortableApps\FirefoxPortable to G:\PortableApps\FirefoxPortable when the issue occurs or similar to from C:\Documents and Settings\User\Documents\FirefoxPortable to C:\Users\User\Documents\FirefoxPortable?
I'm pretty sure full path moves were working in FF 3.x with a launcher update I did a while back but it could have changed in FF 4.x. Can you also let me know what version you're seeing this issue on?
Sometimes, the impossible can become possible, if you're awesome!
Both. It's a different drive letter as well as a different tree structure.
Where are these paths stored? Perhaps I can code something to change them on the fly.
Drive letter updates probably are working properly. But path changes are not. Those are basically the two types of 'moves' for a portable app. I could have sworn we'd nailed this down previously. Can you let me know an example extension that has a compatibility update that is having this issue for you? I ask as compatibility updates are stored independently of extensions and extensions configurations. A compatibility update is basically addons.mozilla.org telling Firefox "yes, I know that extension says it only works with 3.0 to 3.5 but it does work with 3.6, too, so you should allow it to run". Essentially, it's an update to the key values of version compatibility without an actual extension update.
Also, I've marked this topic a bug so we can track it better.
Sometimes, the impossible can become possible, if you're awesome!
KeyConfig and MenuManipulator (both can be found here: http://mozilla.dorando.at/readme.html) are two I constantly have to deal with. KeyConfig just got an XPI update, so that's a temporary workaround (until it comes up again).
Omnibar 0.7.2.20110110
FF Rocker 0.2
Those fail every time. There are another three or four I can add if you need others.
I have the path name difference between computers that you suspect. Same drive letters though (I think).
Using Firefox Launcher 1.6.9.0
jpe
I'm currently working with FFP 3.6.15. I haven't even touched 4.0 yet.
you probably should however update to FFP 3.6.16 (for any patches/security updates it may have)
https://portableapps.com/apps/internet/firefox_portable/localization#leg...
This has been fixed in 5.0. We'll do a legacy release for the now-outdated versions of Firefox with this fix as well in the next week or two.
UPDATE: This is also fixed in the new 3.6.18 Legacy release of Firefox Portable.
Sometimes, the impossible can become possible, if you're awesome!