upgrading and switching back to any version is really easy. Download the zip, extract, voilà. we try hard (really hard) to not break backward compatibility, and if we do, we consider the "breakage" as a bug to fix, unless the "breakage" is indeed a bug (i.e. something that NEEDED to be fixed because of security issues, and so on...)
as for upgrading directly from the admin interface, the problem is that web2py isn't really doing something magic with that button.... it downloads the latest archive and tries to extract it over the current version. The fact that it is marked a experimental (and it probably always be) is that web2py can run under so many architectures, webservers, run with different permissions, etc, that some times it's just impossibile for the web2py process to overwrite the contents of the folder. Anyway, since it's just THAT easy to switch versions (wether going back or forward), it's not a big problem. On Sunday, September 28, 2014 7:44:31 PM UTC+2, Marko Poutiainen wrote: > > I made a simple application with web2py > version 2.4.6-stable+timestamp.2013.04.06.17.37.38 and thought about > upgrading to the latest one because someone else wants to use the same > application on their server. No point in installing an old version, IMO, so > I'll update our version first. Do I run into problems, i.e. has the > framework changed so that it's not backwards compatible to that version? > > And should the upgrade from the admin interface work? There's a warning > that it's still experimental. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
