InstallTrigger.getVersion seems to just be returning "" for all components. I have Linky installed and InstallTrigger.getVersion("linky") returns "" 20030601 has InstallTrigger.getVersion been removed by security?????
Did you install Mozilla to a different path? The version of an add-on is stored path-dependent in mozver.dat (ie. C:\winnt\mozver.dat on Win2k). This is very unfortunate, because using Mozilla from different paths with the same profile can't read the version correctly, if the addon has been installed using the other Mozilla: Imagine having several nightlies installed, let's say to <yesterdayspath> and <todayspath>, that both use the same profile. Imagine an addon <a> that relies upon a certain version <vb> of another addon <b> to be installed. Imagine installing <b> into the profile from <yesterdayspath>. A call to InstallTrigger.getVersion("<b>") will result in <vb>. Imagine installing now <a> from <todayspath>. A call to InstallTrigger.getVersion("<b>") will result in |null|. This renders version testing with profile installation pretty useless in roaming and development situations.
OS: Windows XP → All
if you install Linky into the users profile directory getVersion returns "" when queried about the version. VR_GetVersion seems to return an error
Summary: InstallTrigger.getVersion stopped working → InstallTrigger.getVersion isn't working with user chrome installed files
Component: Installer: XPI Packages → Installer
QA Contact: agracebush → general
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
old XPFE installer is dead.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.