612278 - www.mozilla.com/bg/firefox/4.0b7/whatsnew/ is shown and there is no bg 4.0b6

Status: RESOLVED WONTFIX

(Firefox :: General, defect)

Description

[Ognyan Kulev]

User-Agent:       Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.0b7) Gecko/20100101 Firefox/4.0b7
Build Identifier: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.0b7) Gecko/20100101 Firefox/4.0b7

I'm using Minefield with bg l10n and when I run Firefox 4.0b7 with bg l10n, the page http://www.mozilla.com/bg/firefox/4.0b7/whatsnew/ is shown but it's 404.

Reproducible: Always

Steps to Reproduce:
1. Run Minefield bg l10n
2. Then run Firefox 4.0 Beta 7 bg l10n

Actual Results:  
http://www.mozilla.com/bg/firefox/4.0b7/whatsnew/ is in a new tab and it's 404

Expected Results:  
No whatsnew page because bg l10n this is not update from beta X (X < 7) to beta 7.

It's possible that the same happens with Firefox 4.0 Beta X with en-US l10n and the running 4.0b7 bg. Something about the condition to show whatsnew is not correct.

Comment 1

[Ognyan Kulev]

It should be noted that this page does have sense although there is no bg l10n for beta 6, e.g. when user manually upgraded from en-US beta or from 3.6. And when there's no l10n, better redirect to en-US/ version.

Another user experienced the issue when upgrading from 3.6.x to 4.0 beta 7.

Comment 2

[Pascal Chevrel:pascalc]

I have fixed the bg page so now it is correctly falling back to en-US content, I am not sure what the user experience should be for people "upgrading" from a stable 3.6 to a beta release, the whatsnew page was designed for people upgrading from beta 6 (and there was no beta 6 in Bulgarian in this specific case), when somebody installs a beta 7 build over their existing 3.6 install, I thought they would see the firstrun page not the whatsnew one.

Comment 3

[Robert Strong (they/them - no direct email)]

Firefox itself displays that page without any involvement by the installer so moving to general

Comment 5

[Terry R.]

Since version 4 is quickly disappearing (I could no longer locate the version to download), I am going to close this bug.  If anyone feels it should be reopened, feel free to do so.