X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

How to enable "Deactivated" extensions

Kuphostiwe

Hi,

I want to know how can I activate extensions with the "Deactivated" word in the Extensions tab via about:config.

Thanks

Hi, I want to know how can I activate extensions with the "Deactivated" word in the Extensions tab via about:config. Thanks

Eminye Imininingwane Yohlelo

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Eminye Imininingwane

FredMcD
  • Top 10 Contributor
4261 izisombululo 59654 izimpendulo
Kuphostiwe

The problem may be the add-on is not compatible to your Firefox.

What's your computer system and Firefox version?

What add-ons are you talking about?

The problem may be the add-on is not compatible to your Firefox. What's your computer system and Firefox version? What add-ons are you talking about?
jscher2000
  • Top 10 Contributor
8775 izisombululo 71736 izimpendulo
Kuphostiwe

Just to be sure, you are viewing your Extensions on the Add-on page? Either:

  • Ctrl+Shift+a (Mac: Command+Shift+a)
  • "3-bar" menu button (or Tools menu) > Add-ons
  • type or paste about:addons in the address bar and press Enter/Return

In the left column of the Add-ons page, click Extensions.

In the list on the right side, if the extension does not have an Enable button (or similar term) then there may be one of the following problems:

  • The extension is not digitally signed by the Add-ons team -- usually this will say something about the extension not being verified (see: Add-on signing in Firefox)
  • The extension is incompatible with multiprocess -- try updating the extension using the small "gear" button above the list, then on that little menu, Check for Updates, to see whether a compatibility update is available
  • The extension is blocked because it causes severe crashing -- there may be specific information on the extension's details page when you click its More link on the Add-ons page
  • If you are using Firefox Beta, which is Firefox 57, "Legacy" extensions can no longer be enabled

If you have a question about a specific extension, can you mention which one it is?

Just to be sure, you are viewing your Extensions on the Add-on page? Either: * Ctrl+Shift+a (Mac: Command+Shift+a) * "3-bar" menu button (or Tools menu) > Add-ons * type or paste '''about:addons''' in the address bar and press Enter/Return In the left column of the Add-ons page, click Extensions. In the list on the right side, if the extension does not have an Enable button (or similar term) then there may be one of the following problems: * The extension is not digitally signed by the Add-ons team -- usually this will say something about the extension not being verified (see: [[Add-on signing in Firefox]]) * The extension is incompatible with multiprocess -- try updating the extension using the small "gear" button above the list, then on that little menu, Check for Updates, to see whether a compatibility update is available * The extension is blocked because it causes severe crashing -- there may be specific information on the extension's details page when you click its More link on the Add-ons page * If you are using Firefox Beta, which is Firefox 57, "Legacy" extensions can no longer be enabled If you have a question about a specific extension, can you mention which one it is?

Umnikazi wombuzo

Hi,

I know that this extension isn't supported in Firefox 57 but I want to know if I can force the use before change to ESR and block the updates.

Thanks

Hi, I know that this extension isn't supported in Firefox 57 but I want to know if I can force the use before change to ESR and block the updates. Thanks
jscher2000
  • Top 10 Contributor
8775 izisombululo 71736 izimpendulo
Kuphostiwe

Force it how?? If it is labeled "Legacy" I think it can only be enabled in the "Developer" Edition or in "Nightly" and it's not guaranteed to work. (There is something you change in about:config in those versions.)

https://www.mozilla.org/firefox/channel/desktop/

Force it how?? If it is labeled "Legacy" I think it can only be enabled in the "Developer" Edition or in "Nightly" and it's not guaranteed to work. (There is something you change in about:config in those versions.) https://www.mozilla.org/firefox/channel/desktop/
jscher2000
  • Top 10 Contributor
8775 izisombululo 71736 izimpendulo
Kuphostiwe

Also, if you switch to ESR, you do not need to block updates because ESR is going to remain on Firefox 52 until around June 2018.

Also, if you switch to ESR, you do not need to block updates because ESR is going to remain on Firefox 52 until around June 2018.

Impendulo Ewusizo

How can I change it in Nightly and Developer for make it work? If I enable it in the ESR, when I launch Beta it auto deactivate the extension.

Thanks

How can I change it in Nightly and Developer for make it work? If I enable it in the ESR, when I launch Beta it auto deactivate the extension. Thanks
jscher2000
  • Top 10 Contributor
8775 izisombululo 71736 izimpendulo
Kuphostiwe

antonio8909 said

How can I change it in Nightly and Developer for make it work? If I enable it in the ESR, when I launch Beta it auto deactivate the extension.

You need to run multiple versions of Firefox on the same computer? Generally speaking, it is best to create separate profiles in that case because the older versions can have problems with the changes made by newer versions. More information:

Regarding the preference in about:config I don't remember what it's called. You may find the information on Reddit where many Developer Edition and Nightly users have been discussing Firefox 57 for the past two months: https://www.reddit.com/r/firefox/

''antonio8909 [[#answer-1014917|said]]'' <blockquote> How can I change it in Nightly and Developer for make it work? If I enable it in the ESR, when I launch Beta it auto deactivate the extension. </blockquote> You need to run multiple versions of Firefox on the same computer? Generally speaking, it is best to create separate profiles in that case because the older versions can have problems with the changes made by newer versions. More information: * [[Use the Profile Manager to create and remove Firefox profiles]] * http://kb.mozillazine.org/Using_multiple_profiles_-_Firefox Regarding the preference in about:config I don't remember what it's called. You may find the information on Reddit where many Developer Edition and Nightly users have been discussing Firefox 57 for the past two months: https://www.reddit.com/r/firefox/

Umnikazi wombuzo

I followed that steps in https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles but it still disable the extension in ESR... :(

I followed that steps in https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles but it still disable the extension in ESR... :(
jscher2000
  • Top 10 Contributor
8775 izisombululo 71736 izimpendulo
Kuphostiwe

You need to change how your ESR and Beta start so they do not use the same profile. Please see the other article I linked. Or change it every time, your choice.

You need to change how your ESR and Beta start so they do not use the same profile. Please see the other article I linked. Or change it every time, your choice.
cor-el
  • Top 10 Contributor
  • Moderator
17540 izisombululo 158604 izimpendulo
Kuphostiwe

Note that a lot of code used by legacy extensions is going to be removed, so even if you can activate the extension in DE then it isn't guaranteed that it will keep working.

  • extensions.legacy.enabled = true
  • Bug 1347507 - Stuff we can remove when XPCOM extensions are no longer supported

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)

Note that a lot of code used by legacy extensions is going to be removed, so even if you can activate the extension in DE then it isn't guaranteed that it will keep working. *extensions.legacy.enabled = true *Bug 1347507 - Stuff we can remove when XPCOM extensions are no longer supported (<i>please do not comment in bug reports<br>https://bugzilla.mozilla.org/page.cgi?id=etiquette.html</i>)

Umnikazi wombuzo

I managed to create another profile with another shortcut but I don't understand why I can't enable old extensions in Firefox Beta... Anyway I selected ESR to stop searching updates. I'm not going to update that version ever...

I managed to create another profile with another shortcut but I don't understand why I can't enable old extensions in Firefox Beta... Anyway I selected ESR to stop searching updates. I'm not going to update that version ever...

Umnikazi wombuzo

In case that anyone is thinking about what extension I need: https://addons.mozilla.org/en-us/firefox/addon/hls-stream-detector/?src=search The developer doesn't want to port it to WebExtensions so that's why I need to have another version of Firefox because I don't want to lose that extension.

In case that anyone is thinking about what extension I need: https://addons.mozilla.org/en-us/firefox/addon/hls-stream-detector/?src=search The developer doesn't want to port it to WebExtensions so that's why I need to have another version of Firefox because I don't want to lose that extension.
cor-el
  • Top 10 Contributor
  • Moderator
17540 izisombululo 158604 izimpendulo
Kuphostiwe

You can't enable old extensions in Beta and Release builds. That is only possible in Developer Edition and Nightly builds.

You can't enable old extensions in Beta and Release builds. That is only possible in Developer Edition and Nightly builds.

Umnikazi wombuzo

cor-el dijo

You can't enable old extensions in Beta and Release builds. That is only possible in Developer Edition and Nightly builds.

It doesn't work in Developer/Nightly

''cor-el [[#answer-1015209|dijo]]'' <blockquote> You can't enable old extensions in Beta and Release builds. That is only possible in Developer Edition and Nightly builds. </blockquote> It doesn't work in Developer/Nightly

Umnikazi wombuzo

cor-el, can you explain me hoe to enable it in Developer? I'll try it again.

Thanks

cor-el, can you explain me hoe to enable it in Developer? I'll try it again. Thanks
cor-el
  • Top 10 Contributor
  • Moderator
17540 izisombululo 158604 izimpendulo
Kuphostiwe

What extensions is this about? Isn't there any Legacy extension that works?

With extensions.legacy.enabled set to true you should at least see them under extensions.

Did you check the Browser Console for messages?

What extensions is this about? Isn't there any Legacy extension that works? With extensions.legacy.enabled set to true you should at least see them under extensions. Did you check the Browser Console for messages? *https://developer.mozilla.org/en/Tools/Browser_Console