"becomes" incompatible with firefox 3 portable

[anonymous]

If the path to firefoxportable changes after uppity has been installed, the plugin suddenly becomes incompatible and can only be fixed by changing the drive letter to match the prior system (not always possible if user does not have admin), or by uninstalling / reinstalling the plugin each time the path changes. This works against the portability of firefox portable. I suspect the issue may be some of the code using absolute pvs. relative path names.

[anonymous]

To add to this, after further research I discovered that it only fails if the directory is moved to another drive letter. Simply changing directories is not enough to break it. Also, once broken, mounting the drive as its original drive letter is not sufficient to fix it - the add-in must be uninstalled and reinstalled.

[t-bone]

I downloaded:

•  http://internap.dl.sourceforge.net/sourceforge/portableapps/Firefox_Portable_3.0_en-us.paf.exe

And installed it into C:\FirefoxPortable. I installed Uppity 1.5 from AMO, and verified that it worked. I then moved the installation folder to the E: drive.

And I get exactly this problem. Confirmed.

*Workaround:* Tools, addons, right-click on uppity, select 'find updates'. Restart and it will work.

[t-bone]

Testing a few random extensions, I find that this does also happen to:

• CustomizeGoogle
• Firefox Showcase

But not:

• NoScript
• WOT
• DownThemAll
• HyperWords
• Undo Closed Tabs Button
• CoolIris Previews

So this usually doesn't happen, but is not isolated to Uppity.

[t-bone]

 http://portableapps.com/node/14503

[t-bone]

I believe I've located the common thread. In all cases, install.rdf says that the extension is not compatible with 3.0 (rather, something like 3.0pre or 3.0b5), but the compatibility information has been updated in AMO.

I believe this is a flaw in either Firefox Portable, or Firefox itself. The compatibility information which is part of the profile is somehow lost. Since the fix is just to repackage with the proper compatibility included, I'll probably just do that.

[anonymous]

Replying to t-bone:

I believe this is a flaw in either Firefox Portable, or Firefox itself. The compatibility information which is part of the profile is somehow lost. Since the fix is just to repackage with the proper compatibility included, I'll probably just do that.

Please respond here with any further findings, especially if it is something that can be corrected on the Firefox Portable side of things. I've got a thread running on portable apps at: portableapps.com/node/14503

[t-bone]

Here's all I really know:

• Firefox can check AMO for updated compatibility information
  • (I think it does this any time, or most times, you install an XPI.)
• It stores that somewhere, and knows next time you start.
• If you move a FF portable profile across drives, it loses this information.
  • At this point, it checks install.rdf in the extension, which doesn't always say the same thing.

I have no idea where or how this is stored and it would take a lot of effort to figure it out. Like I said, simply updating install.rdf in the XPI is significantly less effort.

[t-bone]

(In [469]) Fixes #172

• Hard code compatibility with "3.0.*" into install.rdf, and upload this to AMO.

[t-bone]

It's long overdue, but I've finally uploaded this fix to AMO.