So web2py would provide helpers to use this JS file upload library? And helper's syntax would be backwards compatible?
In the mean time, for anyone else searching for upgrade advice, here is how I look at it: upgrading web2py and upgrading anything within an application running on web2py, are two different things. I consider any contents of any of my web2py applications *not* to be a part of web2py itself. Even if some of their parts originally shipped as a part of the Welcome application. So, if I run my entire existing app, unchanged, on a newer version of web2py than it was developed with, I'd expect backwards compatibility for all non-experimental functionality of web2py I used. One of the great features of web2py framework... But if I ever change anything within my app, ie. update jQuery, web2py.js, etc., I fully expect I have to do compatibility tests to see if my code still works as intended. I think it's technically impossible to ie. achieve full backward and forward compatibility with different combinations of jQuery, web2py.js, other custom js code, etc. within an application. It just can't be done. So, assume if you upgrade one of these components, things will break. Further, I'd strongly advice against performing web2py updates and app updates at the same time. Too many different things that could go wrong. Regards, Ales On Tuesday, January 15, 2013 1:38:15 PM UTC+1, weheh wrote: > > On Tuesday, January 15, 2013 1:39:54 AM UTC+8, Massimo Di Pierro wrote: > >> What did you upgrade from? What specifically changed that broke your >> code? > > > Upgrade was from 2.1.x. I tried to trace down exactly what broke the code, > but may have wiped out the tracks accidentally by changing some code in > another place. Nonetheless, when I have some more time this week I'll go > back and try to trace it through again. > > >> >> When you upgrade web2py we do not upgrade web2py.js in your applications. >> > > Yes, I know. However, I try to keep web2py.js up to date as best as > possible. > > >> >> The fact that form uploads is second citizen is not a web2py issue. It is >> an Ajax issues. >> > > Yes, I am well aware of this. > > >> Ajax does not support multipart forms. >> I am not award of a satisfactory solution to this problem unless we >> implement our own custom ajax data encoding. I do not think that would be a >> good idea. >> > > No, I am not suggesting this. I am suggesting, instead, that we package up > a jquery single-file uploader and ship it with web2py so that it becomes a > standard *tested* way of uploading files from a component. It seems like > this has already been done with the menu system and possibly other stuff > inside web2py. I don't think it would be inconsistent to make a component > file uploader a standard part of the tool as well. > > As for claiming this is the third time, I did hedge a little by saying it > was "possibly" the 3rd time. I haven't kept good enough notes to be sure of > this. > > My action item is to trace things through and try to identify the > web2py.js code that's causing the problems. > > --
