Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Firefox Beta release notes redirect to 404 page

  • 5 отговора
  • 2 имат този проблем
  • 6 изгледи
  • Последен отговор от AliceWyman

more options

Firefox beta installer offers a link to "Details" when a new version is available. However this link has been broken in the last releases. Version 28 sends me to the following invalid page: https://www.mozilla.org/en-US/firefox/28.0/releasenotes/

The correct page is: https://www.mozilla.org/en-US/firefox/28.0beta/releasenotes/

Firefox beta installer offers a link to "Details" when a new version is available. However this link has been broken in the last releases. Version 28 sends me to the following invalid page: https://www.mozilla.org/en-US/firefox/28.0/releasenotes/ The correct page is: https://www.mozilla.org/en-US/firefox/28.0beta/releasenotes/

Избрано решение

Всички отговори (5)

more options

Yes, I see the same thing when I go to the Options window - Advanced panel in Firefox 28 Beta, select the Update tab, then click on the Show Update History button and finally click on Details (See my screenshot).

The people who answer questions here, for the most part, are other Firefox users volunteering their time (like me), not Mozilla employees or Firefox developers. I'll escalate this to see if a Mozilla employee can look into the matter and possibly file a bug report.

more options

Hey Schiavini and Alice, I will send an email out and create a bug to see who develops this.

more options

Thank you both! When you've created the bug, please send us the link so I can mark the question as answered.

more options

Избрано решение

Bug 971351 was filed for this. It has now been fixed and the original URL now works:

https://www.mozilla.org/en-US/firefox/28.0/releasenotes/

more options

@Paul McLanahan Thanks for the bug fix and for your followup post here.