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

Install an extentension from core\browser\extensions\ fails

  • 1 reply
  • 5 have this problem
  • 24 views
  • Last reply by cor-el

more options

I am using Firefox Developer Edition by extracting core/* from setup.exe. https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/ installs fine by: - setting these

// Activate extensions in core user_pref("extensions.autoDisableScopes", 11); // 15 - 4 = ALL - SCOPE_APPLICATION user_pref("extensions.enabledScopes", 5); // 15 - 8 - 2 = ALL - SCOPE_SYSTEM - SCOPE_USER

- downloading .xpi - renaming to its id: uBlock0@raymondhill.net.xpi - moving to core\browser\extensions\ - starting Firefox

Doing the same with https://addons.mozilla.org/en-US/firefox/addon/always-right/ fails with: "could not be verified for use in Firefox Developer Edition and has been disabled." It can be installed from AMO, and also from the xpi file by opening it.

Please help me. https://github.com/autonome/Always-Right/issues/1

I am using Firefox Developer Edition by extracting core/* from setup.exe. https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/ installs fine by: - setting these // Activate extensions in core user_pref("extensions.autoDisableScopes", 11); // 15 - 4 = ALL - SCOPE_APPLICATION user_pref("extensions.enabledScopes", 5); // 15 - 8 - 2 = ALL - SCOPE_SYSTEM - SCOPE_USER - downloading .xpi - renaming to its id: uBlock0@raymondhill.net.xpi - moving to core\browser\extensions\ - starting Firefox Doing the same with https://addons.mozilla.org/en-US/firefox/addon/always-right/ fails with: "could not be verified for use in Firefox Developer Edition and has been disabled." It can be installed from AMO, and also from the xpi file by opening it. Please help me. https://github.com/autonome/Always-Right/issues/1

Chosen solution

I checked the signedState in the extensions.json file and notice signedState: 1

This means SIGNEDSTATE_PRELIMINARY: 1 - Add-on is preliminarily reviewed That might be the cause that the extension only works when installed in the profile folder. Other extensions that work may have:

  • SIGNEDSTATE_SIGNED: 2 - Add-on is fully reviewed
Read this answer in context 👍 1

All Replies (1)

more options

Chosen Solution

I checked the signedState in the extensions.json file and notice signedState: 1

This means SIGNEDSTATE_PRELIMINARY: 1 - Add-on is preliminarily reviewed That might be the cause that the extension only works when installed in the profile folder. Other extensions that work may have:

  • SIGNEDSTATE_SIGNED: 2 - Add-on is fully reviewed