Firefox Extensions Compatability Issue
Hi Guys
I've got a packaging job where I'm trying to perform a silent installation of 3 firefox extensions and it's not making it easy on me. I was wondering if anyone had any experience they could share as I'm quickly running out of ideas.
Modify Headers 0.6.6 https://addons.mozilla.org/en-US/firefox/addon/967
wmlbrowser 0.7.20 https://addons.mozilla.org/en-US/firefox/addon/62
XHTML Mobile Profile https://addons.mozilla.org/en-US/firefox/addon/1345
Plan A:
Use firefox.exe -install-global-extensions to unpack the xpi's into the firefox\extensions directory, wrap into an MSI and deploy. This seemed like the most obvious solution to addon deployment and should work. However, when using -install-global-extensions the addons show up as not compatable with the current version of firefox and were disabled.
I tested installing the addons manually and this worked so on with Plan B:
Plan B:
I wrote a script that capture the profile directory that firefox puts down and copies across the extensions, triggered by Active Setup. The result: The same not compatable error received when using -install-global-extensions.
Plan C:
Use firefox portable to create a seperate firefox package that can exist independantly of the main supported firefox installation. Install the requred extensions to it and present it as a seperate icon to the user. The result: Created a firefox portable directory that worked and launched the desired configuration, tested by copying the directory to another machine and launching it. The addons were suddenly incompatable again.
Any help would be extremely appreciated. This problem is proving a lot more difficult then it should be.
I've got a packaging job where I'm trying to perform a silent installation of 3 firefox extensions and it's not making it easy on me. I was wondering if anyone had any experience they could share as I'm quickly running out of ideas.
Modify Headers 0.6.6 https://addons.mozilla.org/en-US/firefox/addon/967
wmlbrowser 0.7.20 https://addons.mozilla.org/en-US/firefox/addon/62
XHTML Mobile Profile https://addons.mozilla.org/en-US/firefox/addon/1345
Plan A:
Use firefox.exe -install-global-extensions to unpack the xpi's into the firefox\extensions directory, wrap into an MSI and deploy. This seemed like the most obvious solution to addon deployment and should work. However, when using -install-global-extensions the addons show up as not compatable with the current version of firefox and were disabled.
I tested installing the addons manually and this worked so on with Plan B:
Plan B:
I wrote a script that capture the profile directory that firefox puts down and copies across the extensions, triggered by Active Setup. The result: The same not compatable error received when using -install-global-extensions.
Plan C:
Use firefox portable to create a seperate firefox package that can exist independantly of the main supported firefox installation. Install the requred extensions to it and present it as a seperate icon to the user. The result: Created a firefox portable directory that worked and launched the desired configuration, tested by copying the directory to another machine and launching it. The addons were suddenly incompatable again.
Any help would be extremely appreciated. This problem is proving a lot more difficult then it should be.
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
MarkRusbridge
14 years ago
Ok, eventually managed to get it sorted.
I could verify that the addons themselves do actually work by manually installing them. So given that we'll be controlling any extensions that go into Firefox anyway I ended up disabling the compatibility checking.
Packaged Firefox using setup capture and including this add-on here: https://addons.mozilla.org/en-US/firefox/addon/51892 (GPO For Firefox) which was installed globally.
I modified the ADM to include extension.checkCompatibility.3.6 and set it to false in the GPO object.
I then had to modify C:\Program Files\Mozilla Firefox\defaults\pref\firefox.js and add the line:
pref("extensions.checkCompatibility.3.6", false);
This pref doesn't exist by default so it needs to be specified before the GPO can control it. For those that don't intend to use GPO objects, lockpref() can be used instead to set it in the package.
I could verify that the addons themselves do actually work by manually installing them. So given that we'll be controlling any extensions that go into Firefox anyway I ended up disabling the compatibility checking.
Packaged Firefox using setup capture and including this add-on here: https://addons.mozilla.org/en-US/firefox/addon/51892 (GPO For Firefox) which was installed globally.
I modified the ADM to include extension.checkCompatibility.3.6 and set it to false in the GPO object.
I then had to modify C:\Program Files\Mozilla Firefox\defaults\pref\firefox.js and add the line:
pref("extensions.checkCompatibility.3.6", false);
This pref doesn't exist by default so it needs to be specified before the GPO can control it. For those that don't intend to use GPO objects, lockpref() can be used instead to set it in the package.
Posted by:
anonymous_9363
14 years ago
Excellent work. Could you post it into the 'Package KB', if you haven't already?
Posted by:
nheim
14 years ago
Hi Mark,
your solution seems to work for you, however, i wouldn't recommend it.
First: Install-global-extension was changed with FF version 3.6. Now, you just drop the XPI into the extensions folder and start FF. It will be detected there and installed.
Second: If you disable the version checking, you open a door for problems. A standard user can install extensions to its profile without any elevated credentials.
With this, there is no guard against REALLY incompatible extensions.
A better solutions: Open the XPI with something like 7zip and extract "install.rdf". Search for the "maxVersion" tag and change it to "3.6.*". Then put the changed. file back into the XPI. That's all.
I am packing FF 3.6 right now and have to to this change on about 2/3 of the extensions we install globally.
Regards, Nick
your solution seems to work for you, however, i wouldn't recommend it.
First: Install-global-extension was changed with FF version 3.6. Now, you just drop the XPI into the extensions folder and start FF. It will be detected there and installed.
Second: If you disable the version checking, you open a door for problems. A standard user can install extensions to its profile without any elevated credentials.
With this, there is no guard against REALLY incompatible extensions.
A better solutions: Open the XPI with something like 7zip and extract "install.rdf". Search for the "maxVersion" tag and change it to "3.6.*". Then put the changed. file back into the XPI. That's all.
I am packing FF 3.6 right now and have to to this change on about 2/3 of the extensions we install globally.
Regards, Nick
Posted by:
MarkRusbridge
14 years ago
Hi Nick
Thanks for your feedback. I don't think having the version checking is going to be a problem. We've disabled XPI installs using a GPO addon, so users would have to go a long way out of their way to get their extensions working. They'd have to unzip the xpi, set the folder to the correct GUID, place it in the neccessary profile directory ect. Also easilly fixed if they call the helpdesk with problems. :)
I appreciate the suggestion though. I'll look at doing it that way with future releases.
Regards, Mark
Thanks for your feedback. I don't think having the version checking is going to be a problem. We've disabled XPI installs using a GPO addon, so users would have to go a long way out of their way to get their extensions working. They'd have to unzip the xpi, set the folder to the correct GUID, place it in the neccessary profile directory ect. Also easilly fixed if they call the helpdesk with problems. :)
I appreciate the suggestion though. I'll look at doing it that way with future releases.
Regards, Mark
Posted by:
nheim
13 years ago
Hi Jane,
if you pack FF by yourself, you just drop the XPI into the extensions folder, like i wrote in post #4.
Regards, Nick
if you pack FF by yourself, you just drop the XPI into the extensions folder, like i wrote in post #4.
Regards, Nick
Posted by:
jfrasier
13 years ago
This is so hard when you don't do this all the time.
I am running this line in a batch file:
\\installation_folder\"Firefox Setup 3.6.15.exe" -ms
I put the gpofirefox_08.xpi in \\installation_folder\Program Files\Mozilla Firefox\extensions
When I run it Firefox installs fine, but no extension. I also tried putting the file folder named with the GUID in the extensions folder and that didn't work either.
What am I doing wrong?
Jane
I am running this line in a batch file:
\\installation_folder\"Firefox Setup 3.6.15.exe" -ms
I put the gpofirefox_08.xpi in \\installation_folder\Program Files\Mozilla Firefox\extensions
When I run it Firefox installs fine, but no extension. I also tried putting the file folder named with the GUID in the extensions folder and that didn't work either.
What am I doing wrong?
Jane
Posted by:
nheim
13 years ago
Hi Jane,
you have to put the XPI-file into the extensions folder AFTER the FF-installation process.
Your FF-install results in a C:\program files\Mozilla Firefox\ folder structure. Start FF once and close it.
Then put the XPI into the extensions folder and start FF again.
Now, the extension will be installed.
Regards, Nick
you have to put the XPI-file into the extensions folder AFTER the FF-installation process.
Your FF-install results in a C:\program files\Mozilla Firefox\ folder structure. Start FF once and close it.
Then put the XPI into the extensions folder and start FF again.
Now, the extension will be installed.
Regards, Nick
Posted by:
jfrasier
13 years ago
Thanks, Nick.
Would there be a way to make it so the addon is installed definitely for all users? When I opened Firefox it asked me to install it and also I had the ability to cancel the installation.
Thanks.
Would there be a way to make it so the addon is installed definitely for all users? When I opened Firefox it asked me to install it and also I had the ability to cancel the installation.
Thanks.
Posted by:
AngelD
13 years ago
See if you can find some useful information at http://kb.mozillazine.org/Installing_extensions
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.