X
Nhấn vào đây để đến phiên bản di động của trang web.

Diễn đàn trợ giúp

Re-Enable addons in older versions?

Được đăng

Since the bug-outbreak thing happened a few days ago, all or most of my addons have stopped working, forcing me to use them as temporary ones. I understand that there was a fix rolled out for the latest version of FireFox but I sadly cannot that version. This whole thing confuses me deeply. I've got into about:config, disabled the need to have them signed, used the addon going around that adds the fix, tried a bunch of methods I saw all over the place but nothing seems to be working. I sadly do need the use of the old addon methods. (Not to mention some other changes visually were just flat out ugly with no fix in sight.)

I'm told all of the past version fixes only work on the 'ESR' versions. Where I'm stuck on FireFox 55.

Is there no way to just force addons to stay on even if not signed in the first place? Or auto-load temporary addons upon FireFox launching?

Since the bug-outbreak thing happened a few days ago, all or most of my addons have stopped working, forcing me to use them as temporary ones. I understand that there was a fix rolled out for the latest version of FireFox but I sadly cannot that version. This whole thing confuses me deeply. I've got into about:config, disabled the need to have them signed, used the addon going around that adds the fix, tried a bunch of methods I saw all over the place but nothing seems to be working. I sadly do need the use of the old addon methods. (Not to mention some other changes visually were just flat out ugly with no fix in sight.) I'm told all of the past version fixes only work on the 'ESR' versions. Where I'm stuck on FireFox 55. Is there no way to just force addons to stay on even if not signed in the first place? Or auto-load temporary addons upon FireFox launching?

Chi tiết hệ thống bổ sung

Phần bổ trợ đã cài đặt

  • Shockwave Flash 32.0 r0

Ứng dụng

  • Chuỗi đại diện người dùng: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:55.0) Gecko/20100101 Firefox/55.0

Thông tin chi tiết

jscher2000
  • Top 10 Contributor
8837 giải pháp 72222 câu trả lời
Được đăng

Hi Arch, why Firefox 55??

Currently there are updates for Firefox 60 ESR and Firefox 66. There was a note on Twitter that Mozilla may release something for unsupported older versions, but for the time being, you would need to install the new certificate for verifying extension signatures a different way, such as installing manually. For an unsupported approach, see: https://support.mozilla.org/questions/1258165#answer-1218833

Hi Arch, why Firefox 55?? Currently there are updates for Firefox 60 ESR and Firefox 66. There was a note on Twitter that Mozilla may release something for unsupported older versions, but for the time being, you would need to install the new certificate for verifying extension signatures a different way, such as installing manually. For an unsupported approach, see: https://support.mozilla.org/questions/1258165#answer-1218833
FredMcD
  • Top 10 Contributor
4300 giải pháp 60395 câu trả lời
Được đăng

jscher2000 solution worked for my v54.

jscher2000 solution worked for my v54.
Được đăng

Người tạo câu hỏi

jscher2000 said

Hi Arch, why Firefox 55?? Currently there are updates for Firefox 60 ESR and Firefox 66. There was a note on Twitter that Mozilla may release something for unsupported older versions, but for the time being, you would need to install the new certificate for verifying extension signatures a different way, such as installing manually. For an unsupported approach, see: https://support.mozilla.org/questions/1258165#answer-1218833

Actually I came across that post by you. I had tried that too. And strangely never worked. I was using my backup browser during the time and just ended up leaving FireFox running for over an hour. I also did try the ESR version too.

''jscher2000 [[#answer-1219742|said]]'' <blockquote> Hi Arch, why Firefox 55?? Currently there are updates for Firefox 60 ESR and Firefox 66. There was a note on Twitter that Mozilla may release something for unsupported older versions, but for the time being, you would need to install the new certificate for verifying extension signatures a different way, such as installing manually. For an unsupported approach, see: https://support.mozilla.org/questions/1258165#answer-1218833 </blockquote> Actually I came across that post by you. I had tried that too. And strangely never worked. I was using my backup browser during the time and just ended up leaving FireFox running for over an hour. I also did try the ESR version too.
jscher2000
  • Top 10 Contributor
8837 giải pháp 72222 câu trả lời
Được đăng

Where did the process break down. If you check the Certificate Manager, is the certificate even listed?

Preferences page > Advanced > Certificates > View Certificates

On the Authorities tab, scroll down to where Mozilla Corp should be listed as the issuer. Anything?

Where did the process break down. If you check the Certificate Manager, is the certificate even listed? Preferences page > Advanced > Certificates > View Certificates On the Authorities tab, scroll down to where Mozilla Corp should be listed as the issuer. Anything?
Được đăng

Người tạo câu hỏi

I actually don't even see Mozilla Corp in there.

When looking in the Ms all I get are theses.

I actually don't even see Mozilla Corp in there. When looking in the Ms all I get are theses.
cor-el
  • Top 10 Contributor
  • Moderator
17670 giải pháp 159841 câu trả lời
Được đăng

There is a legacy system add-on planned for older Firefox versions that do not support the hotfix.

  • Bug 1549604 - ship legacy system add-ons to remediate armagadd-on 2.0
There is a legacy system add-on planned for older Firefox versions that do not support the hotfix. *[https://bugzilla.mozilla.org/show_bug.cgi?id=1549604 Bug 1549604] - ship legacy system add-ons to remediate armagadd-on 2.0