[web2py] Re: Burned by web2py.js ... again

2013-01-15 Thread weheh
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

[web2py] Re: Burned by web2py.js ... again

2013-01-15 Thread LightDot
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

[web2py] Re: Burned by web2py.js ... again

2013-01-14 Thread Massimo Di Pierro
What did you upgrade from? What specifically changed that broke your code? When you upgrade web2py we do not upgrade web2py.js in your applications. The fact that form uploads is second citizen is not a web2py issue. It is an Ajax issues. Ajax does not support multipart forms. I am not award

[web2py] Re: Burned by web2py.js ... again

2013-01-14 Thread Niphlod
the only problems I encountered are the changes of the encodings/escaping for web2py-component-command and web2py-component-flash headers had a little of problems rewriting semi-custom implementation for flash messages and component-reloading with all the escape/unescape/decodeURIComponent

[web2py] Re: Burned by web2py.js ... again

2013-01-14 Thread Massimo Di Pierro
whehe claims this is the third time. We only changed the behavior of this once as far as I can remember. On Monday, January 14, 2013 2:57:08 PM UTC-6, Niphlod wrote: the only problems I encountered are the changes of the encodings/escaping for web2py-component-command and