374897 - first page upon installing old firefox says You've updated to latest ...

Status: RESOLVED DUPLICATE of bug 538486

(www.mozilla.org :: General, defect)

Description

[Tad W]

User-Agent:       Mozilla/5.0 (compatible;)
Build Identifier: 

I installed firefox 2.0.0.2 was expecting an update to be necessary and was greeted with "You've updated to the lastest version." This is obviously incorrect and confuses users.  I also see http://en-us.www.mozilla.com/en-US/firefox/2.0.0.1/whatsnew/ has the same problem.  There should be (probably is) a script to fix this each time a new release comes out.

Reproducible: Always

Steps to Reproduce:
1. Install Firefox 2.0.0.1 or 2.0.0.2
2. Run it
Actual Results:  
I'm told it's up-to-date

Expected Results:  
Page should state that a newer version is available and say to check for updates and optionally offer a link to the download page.

Comment 1

[Mike Beltzner [:beltzner, not reading bugmail]]

-> AUS

Comment 2

[:Gavin Sharp [email: [e-mail]]]

This really isn't an AUS bug, as far as I can tell... The fix for this would need to be on either the client side or on the web site, and adding UA detection of some sort to the "You've updated" page would probably be easiest.

Comment 3

[Pascal Chevrel:pascalc (PTO until April 26)]

The welcome page for a new user isn't:
http://en-us.www.mozilla.com/en-US/firefox/2.0.0.1/whatsnew/ 

but :
http://en-us.www.mozilla.com/en-US/firefox/2.0.0.1/firstrun/

AFAIK, the whatsnew page is displayed only after an automatic update.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

(In reply to comment #3)
> AFAIK, the whatsnew page is displayed only after an automatic update.

In general, that's true, but it's also shown in a scenario such as "install Firefox 0.9, run it once, uninstall it, install Firefox 2.0.0.2 2 years later.", since we store the "last version" information in the profile.

Comment 5

[Pascal Chevrel:pascalc (PTO until April 26)]

ah ok, then we should indeed add some version detection for these cases and redirect people to the welcome page, the easiest way would probably via js or php on the website.

Comment 6

[Tad W]

This is ok, but seems unnecessary.  When I said "script to fix this each time a new release comes out" I was thinking just a simple script on the server to change the html to say a newer version available.  This wouldn't bother the server since the code is run only once when new updates are released, and furthermore the script code is not exposed to the web.  The benefits are less work for the server (if php) and no problems if the client is not running js or does not have default useragent string.

Comment 7

[Tad W]

If it's not obvious, by script I mean shell/perl/something of that nature.  Above (if php) should be (vs. php)

Comment 8

[Tad W]

super simple solution:

have 2 versions of this page: latest_version & newer_version_available

store them in something like parent directory of 2.0.0.2
make http://en-us.www.mozilla.com/en-US/firefox/2.0.0.2/whatsnew/ and similar a symlink to newer_version_available
make http://en-us.www.mozilla.com/en-US/firefox/2.0.0.3/whatsnew/ symlink to latest_version

now update script is just two lines:
create symlink for the new version that points to latest_version
replace symlink for last version so it points to new_version_available

Comment 10

[Alexander Yuan]

By the way, this seems to be a duplicate of Bug 390332.