Enabling plugins using locked preferences
I have legacy plugins that need to stay enabled. I've learned you can disable checking the blocklist with extensions.blocklist.enabled, but this doesn't re-enable plugins that were previously disabled.
Is it possible to enable specific plugins in a way that can be deployed to a large organization?
Modified by JasonNVSD
Helpful replies
as far as i know this can't be done in about:config unfortunately, since the pluginreg.dat file is the only place where the information about the status of plugins is stored. one thing you could try on a machine level is to move the location of the plugin's .dll file (maybe to the \plugins subfolder inside the firefox installation directory), then it may be re-detected and treated as new plugin which should be set to active...
Go to answer 1Additional System Details
Installed Plug-ins
- Adobe PDF Plug-In For Firefox and Netscape "9.5.3"
- Next Generation Java Plug-in 1.6.0_16 for Mozilla browsers
Application
- User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
More Information
hello jason, you could try to delete the file named pluginreg.dat in the affected profiles, then all the present plugins will be set to active again...
Question owner
I would need it to apply to the machine and not just users, just like locked preferences overrides the user profiles.
It would also be nice if I could enable specific plugins since there are other disabled plugins that would best remain disabled.
Helpful Reply
as far as i know this can't be done in about:config unfortunately, since the pluginreg.dat file is the only place where the information about the status of plugins is stored. one thing you could try on a machine level is to move the location of the plugin's .dll file (maybe to the \plugins subfolder inside the firefox installation directory), then it may be re-detected and treated as new plugin which should be set to active...
Question owner
I figured out you can refer to specific add-ons in preferences using extensions.<GUID>.property, but I couldn't find any documentation and it appears to only work on themes and extensions and not plugins.
Modified by JasonNVSD