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

Diễn đàn trợ giúp

will the add on bug be fixed on OLDER versions of FireFox

Được đăng

I am sorry to write you all about this seeing as the forums are going about it, but since I cannot find my answer in them (and I seem to be limited to 3 posts due to being a newbie) I figured I would just write in and ask. Will the add on bug thats going on also be fixed for versions such as 52.9.0 (32-bit) which I use. Upgrading to a newer version is not an option for me as i am on an older OS (and my pc is a potato lol) Thanks in advance.

I am sorry to write you all about this seeing as the forums are going about it, but since I cannot find my answer in them (and I seem to be limited to 3 posts due to being a newbie) I figured I would just write in and ask. Will the add on bug thats going on also be fixed for versions such as 52.9.0 (32-bit) which I use. Upgrading to a newer version is not an option for me as i am on an older OS (and my pc is a potato lol) Thanks in advance.
Trích dẫn

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

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

  • PlayNow Plugin
  • Version 5.41.3.0
  • Google Update
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Next Generation Java Plug-in 11.191.2 for Mozilla browsers
  • Shockwave Flash 32.0 r0
  • Adobe Shockwave for Director Netscape plug-in, version 12.2.4.194
  • 5.1.50709.0
  • Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
  • Yahoo Application State Plugin version 1.0.0.7

Ứng dụng

  • Chuỗi đại diện người dùng: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Firefox/52.0

Thông tin chi tiết

philipp
  • Top 25 Contributor
  • Moderator
5281 giải pháp 23331 câu trả lời
Được đăng

hi, till now the priority was on fixing currently supported versions. i think there are no concrete plans on how to deal with older versions yet, that is likely something that will be decided during the coming week...

hi, till now the priority was on fixing currently supported versions. i think there are no concrete plans on how to deal with older versions yet, that is likely something that will be decided during the coming week...
Bài viết này có hữu ích với bạn không?
Trích dẫn

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

I see... hmm I better make plans then to possibly need to move to a different browser and remove fireFox then just in case it comes to that :(

I see... hmm I better make plans then to possibly need to move to a different browser and remove fireFox then just in case it comes to that :(
Bài viết này có hữu ích với bạn không?
Trích dẫn
James
  • Moderator
1593 giải pháp 11223 câu trả lời
Được đăng

Note for the old EOL Windows XP and Vista you are very limited on web browser options as none of the major web browsers still support XP and Vista.

Chromium, Chrome, Opera dropped support of the EOL XP and Vista back in April 2016.

Firefox 52.9.0esr was Released back on June 26, 2018.

It is possible Mozilla may make an exception with a minor update for the EOL Firefox 52 ESR like say 52.9.1esr to help people get their affected extensions working again.

The issue was not with any Firefox version but with a unintentional situation in which a intermediate certificate that many used had for many extensions and such had expired.

Besides using Windows 7 or later you could consider dual booting with a light 32-bit Linux distro with a light desktop like Xfce. This will allow you to use current Firefox versions and also fully support the HTML5 players many sites use now days.

Note for the old EOL Windows XP and Vista you are '''very limited on web browser options as none of the major web browsers still support XP and Vista'''. Chromium, Chrome, Opera dropped support of the EOL XP and Vista back in April 2016. Firefox 52.9.0esr was Released back on June 26, 2018. It is possible Mozilla may make an exception with a minor update for the EOL Firefox 52 ESR like say 52.9.1esr to help people get their affected extensions working again. The issue was not with any Firefox version but with a unintentional situation in which a intermediate certificate that many used had for many extensions and such had expired. Besides using Windows 7 or later you could consider dual booting with a light 32-bit Linux distro with a light desktop like Xfce. This will allow you to use current Firefox versions and also fully support the HTML5 players many sites use now days.

Được chỉnh sửa bởi James vào

Bài viết này có hữu ích với bạn không?
Trích dẫn
OnThePike 1 giải pháp 16 câu trả lời
Được đăng

Go to about:config

Search for xpinstall.signatures.require

Double click it to set to false.

Wait a few seconds. Your add-on's should come back to life.


My issue was somewhat resolved using

xpinstall.signatures.require = true and setting it to false.

However, now that the disabled add-on's are re-enabled, each of them is highlighted in yellow with an unsupported notification.

Go to about:config Search for xpinstall.signatures.require Double click it to set to false. Wait a few seconds. Your add-on's should come back to life. My issue was somewhat resolved using xpinstall.signatures.require = true and setting it to false. However, now that the disabled add-on's are re-enabled, each of them is highlighted in yellow with an unsupported notification.
Bài viết này có hữu ích với bạn không?
Trích dẫn
jscher2000
  • Top 10 Contributor
8577 giải pháp 70121 câu trả lời
Được đăng

OnThePike said

Go to about:config Search for xpinstall.signatures.require Double click it to set to false.

This introduces the risk of rogue updates, so you should consider also disabling extension auto-updates with this setting so you'll have the opportunity to inspect and reject any questionable extension updates:

extensions.update.autoUpdateDefault => false

With that setting, when an update is detected, a new category will appear on the Add-ons page listing available updates.

''OnThePike [[#answer-1219715|said]]'' <blockquote> Go to about:config Search for xpinstall.signatures.require Double click it to set to false. </blockquote> This introduces the risk of rogue updates, so you should consider also disabling extension auto-updates with this setting so you'll have the opportunity to inspect and reject any questionable extension updates: extensions.update.autoUpdateDefault => false With that setting, when an update is detected, a new category will appear on the Add-ons page listing available updates.
Bài viết này có hữu ích với bạn không?
Trích dẫn
cor-el
  • Top 10 Contributor
  • Moderator
17342 giải pháp 156773 câu trả lời
Được đăng

Câu trả lời hữu ích

See also Mozilla Add-ons on Twitter: "The current plan is to push an update to update versions older than 64, but the current ETA is sometime Monday"

See also Mozilla Add-ons on Twitter: "The current plan is to push an update to update versions older than 64, but the current ETA is sometime Monday" *https://twitter.com/mozamo/status/1124698401046577153
Bài viết này có hữu ích với bạn không? 1
Trích dẫn
Đặt một câu hỏi

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.