Checking for upgrades isn't working as I expected (1.99.7 installed)

[Tim Richardson]

I'm a new user so I don't know what should happen when a new stable release occurs.
I have 1.99.7 source running on a Windows 2003 server. Python 2.7 (ActiveState). Browser is Firefox. Server is Rocket 1.2.4 on port 8010
In the Admin home page under the version string (1.99.7) it reports "checking for upgrades..." and that never completes ( I mean, that message doesn't change)

regards

Tim

[Don_X]

Hello Tim,
Welcome to web2py-users group !

Considering that you are new ! and probably you have not developed any apps yet in your web2py installation ( the 1.99.7 ) ...
you can simply  make a new install of the latest stable version ( now is the 2.0.5 ) ... under another folder if you want !

the checking for upgrades button does not work and no one actually noticed it until it was time to upgrade to the latest version ( which is recently .. ) .. before the 1.99.7 (minus - ) it used to work fine !
That being said ! ...  it should not stopped you from getting your feet wet with the latest web2py version which is awesome !

happy coding !

Don_X

[Massimo Di Pierro]

There is a bug in 1.99.7 that prevents automatic upgrades. This is fixed in 2.0.x but you cannot upgrade from the older versions via the web. 

Anyway, upgrade consists in unzipping new version over old version.

[Bruno Rocha]

If you have access to files (ssh or ftp) you can try to edit this line

 File "...web2py/applications/admin/controllers/default.py", line 113, in check_version



    + XML(' <strong class="upgrade_version">%s</strong>' % version_number)

and change to

    + XML(' <strong class="upgrade_version">%s</strong>' % str(version_number))

Including str(version_number) and saving, now you can try to click on check for upgrade and it will work!

[Tim Richardson]

New user, but web2py is so productive I already have three apps in production, one using the scheduler. I'll be upgrading carefully, in fact I will do a parallel installation. It seems that it's probably worthwhile manually updating some existing standard files in each app, although I haven't researched this yet, but I assume it's well documented somewhere. (I've gathered it's javascript files, and the administration page)

[Mandar Vaze]

Bruno : Thanks for the tip.

The "upgrade" was broken (for me at least) on 2.0.2 

I didn't get notification to upgrade to 2.0.6 (It would remain stuck in "checking for upgrades")

Your suggestion worked well.

-Mandar

[Le Don X]

Indeed ! ... Bruno is tha Man !