[SOLVED] - Firefox 27 Deployment: Extensions Not Enabled, Plugins Not Loaded
Although nearly every machine (north of 2000) has Firefox installed, we have groups of 20-100+ machines with a variety of versions of Firefox going all the way back to 3.6.13. (I have over 1k machines with some version of 3.6!) I'm trying to correct that and get everyone on the latest, which is 27.0.1 at the time of writing. I have what may amount to a highly customized install because we're trying to achieve a specific & consistent configuration.
In test deployments of Firefox 27.0.1, with the exception of Adobe Acrobat, none of our core extensions & plugins are enabled and loaded.
Something about my custom configuration is invalid or incorrect, likely due a misunderstanding on my part.
REFERENCES: I've tried to keep track of the resources I've used to get where I am today, but I may have missed a few.
http://kb.mozillazine.org/About:config_entries https://support.mozilla.org/en-US/kb/common-questions-after-upgrading-firefox-36 https://developer.mozilla.org/en-US/Add-ons/Installing_extensions https://wiki.mozilla.org/Deployment:Deploying_Firefox http://stealthpuppy.com/prepare-mozilla-firefox-for-enterprise-deployment-and-virtualization/ https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options http://www.mockbox.net/server-stuff/configmgr-sccm/174-install-and-configure-firefox-silently
Several resources on Mike.kaply.com
http://mike.kaply.com/2012/02/21/understanding-add-on-scopes/ http://mike.kaply.com/2012/03/22/customizing-firefox-advanced-autoconfig-files/ http://mike.kaply.com/2012/03/20/customizing-firefox-autoconfig-files-continued/ http://mike.kaply.com/2012/03/16/customizing-firefox-autoconfig-files/ http://mike.kaply.com/2012/03/15/customizing-firefox-default-preference-files/ and much much more
Phylum மூலமாக திருத்தப்பட்டது
தீர்வு தேர்ந்தெடுக்கப்பட்டது
Thanks for the response - greatly appreciate it.
I'm short on time so I'll only speak to the extension & plugins: We do have an extension called Research Monitor. Initially when installed, if one checks 'Extensions', its listed there. But after a 'little while' if one checks again, the extension disappears and a new Research Monitor plugin appears. I don't understand why that is, but as long as it works, I don't care. :)
However the main point I'm trying to overcome is:
- If I do a vanilla install of Firefox, Firefox see's all our extensions & plugins, and they're all enabled & loaded.
- If I run my customized install of Firefox, it only loads the Adobe plugin.
This suggested there was something screwy with my config.
Well I finally found it & as I suspected, a misunderstanding on my part: defaultPref("plugin.scan.plid.all",false);
That should've been set to true, or eliminated from the config altogether.
Read this answer in context 👍 0All Replies (6)
I included a lot more in the 'Troubleshooting Information' section that's under the 'MORE SYSTEM DETAILS' link. If it should be pasted here, please let me know.
Hoping a bump might attract some attention. So
- bump*
This sounds like quite a complicated setup that you try to achieve.
I don't know if there is someone around here that has the background and expertise to provide you with this information.
Note that the correct name is extensions.autoDisableScopes (see bug Bug 666437 and Bug 693698) and that this pref only has effect for extensions and not for plugins.
Plugins are always found via a scan in known locations.
To initialize prefs it is best to do this via a mozilla.cfg file or via means like distribution.ini.
- http://mike.kaply.com/2012/03/26/customizing-firefox-distribution-ini/
- http://mike.kaply.com/2012/03/16/customizing-firefox-autoconfig-files/
http://mike.kaply.com/2012/02/09/integrating-add-ons-into-firefox/
See also:
- CCK2 Wizard: https://addons.mozilla.org/firefox/addon/cck2wizard/
There is no need to include prefs like these that have an epoch time string as those will be created automatically when required (1273520281 is May 10 2010, so that is really old) This value also makes no sense as it should be a time in seconds (the default of 43200 would be twice a day 86400/2)
- defaultPref("app.update.interval", 1273520281);
The CAPS prefs (capability.policy.*) are probably no longer supported and won't have effect, so you may want to reconsider which prefs that you really want to initialize.
தீர்வு தேர்ந்தெடுக்கப்பட்டது
Thanks for the response - greatly appreciate it.
I'm short on time so I'll only speak to the extension & plugins: We do have an extension called Research Monitor. Initially when installed, if one checks 'Extensions', its listed there. But after a 'little while' if one checks again, the extension disappears and a new Research Monitor plugin appears. I don't understand why that is, but as long as it works, I don't care. :)
However the main point I'm trying to overcome is:
- If I do a vanilla install of Firefox, Firefox see's all our extensions & plugins, and they're all enabled & loaded.
- If I run my customized install of Firefox, it only loads the Adobe plugin.
This suggested there was something screwy with my config.
Well I finally found it & as I suspected, a misunderstanding on my part: defaultPref("plugin.scan.plid.all",false);
That should've been set to true, or eliminated from the config altogether.
Phylum மூலமாக திருத்தப்பட்டது
I considered leveraging Mike Kaply's CCK2, which is great honestly, but felt comfortable doing it manually. I'll leverage the CCK2 for the next push & see how that works.
Thanks again for taking a peek at this post and providing invaluable insight.
I considered leveraging Mike Kaply's CCK2, which is great honestly, but felt comfortable doing it manually. I'll leverage the CCK2 for the next push & see how that works.
Thanks again for taking a peek at this post and providing invaluable insight.