too many scaring advices here... first and foremost, if you have two web2py "roots" in any given (and separate) folders, they'll work without hiccup.
second: if you copy your entire application (the folder applications/appname) from "old web2py" to "new web2py" you can test the functionality on the "new" while keeping a safe-copy in the old. Additional care "should" be taken on the sessions/ folder and the cache/ one (i.e. they should be cleaned to ensure proper functionality moving the app between web2py versions) third: when web2py is updated, it's best to copy over also the appadmin.py controller and static/js/web2py.js: this is ALWAYS safe, although is not always required. web2py.js is where the main hooks for ajax functionality resides and those are linked to "python code" in web2py, so when "python code" changes, web2py.js gets the new features accordingly. Everything else is "application-dependant", so as long as you coded things following the documentation, they SHOULD NOT brake. I mean, if they break (they can, but we work hard in order not to), then you found a bug that will be fixed. -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
