This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Enabling plugins using locked preferences

  • 4 replies
  • 1 has this problem
  • 4 views
  • Last reply by JasonNVSD

JasonNVSD
JasonNVSD
more options

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?

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

All Replies (4)

philipp
philipp
  • Moderator
more options

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...

JasonNVSD
JasonNVSD Question owner
more options

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.

philipp
philipp
  • Moderator
more options

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...

JasonNVSD
JasonNVSD Question owner
more options

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