We recently updated a somewhat complex app from web2py 1.99.4 to 2.4.2 and it was pretty straightforward. Going to 2.4.6 should be exactly the same. Do make backups and test everything before going live.
Things that required intervention were experimental features of web2py that we used, such as the scheduler. We also updated appadmin, web2py_ajax, web2py.js within the app, and went further to update jquery, calendar (had a bug related to date manipulation) and modernizer. Than we needed to audit all 3rd party js libs, but that was expected. No big surprises there either, just needed to update a couple of them because of the newer jquery. Note, we never use automatic upgrades from the admin, but I'm not aware of any open bugs related to this feature. Regards, Ales On Thursday, May 9, 2013 5:01:49 PM UTC+2, George Hellman wrote: > > I am trying to upgrade web2py automatically > > I am running > "Version 1.99.4" " Running on Apache/2.2.20 (Ubuntu)" > (ubuntu server) with full root access. > > It says: "Checking for upgrades..." or, if there is an upgrade button, it > does not upgrade. > > This may have to do with "file locking" as on post said. > How do I get Ubuntu to allow an upgrade? > > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
