Looking further into the script, it also uses InstallTrigger.compareVersion. I am trying to contact our Sametime support group to find out if this is a custom written script by them or if this is the original IBM/Lotus version of this script.
I also found out from out Sametime support group that we will be upgrading to a version that does not have this issue next week. So, I guess if this does not turn out to be an issue for anyone else, it is then no longer an issue.
This is a problem for us as well. Our IT department will not upgrade any time soon.
Since the whole rest of the xpinstall script processing code was removed as well would the plugin install even if .getVersion() is still present? In FF3 only ExtensionManager (install.rdf) type installs work and plugins tended to use the old install.js style.
I have no (In reply to comment #5) > Since the whole rest of the xpinstall script processing code was removed as > well would the plugin install even if .getVersion() is still present? In FF3 > only ExtensionManager (install.rdf) type installs work and plugins tended to > use the old install.js style. > I have no idea. All I know is that before the checkin for bug 406807 this worked just fine and since then it does not.
This problem went away quite some time ago. ->> WORKSFORME
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.