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 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 and 
> so on....but aside that, all is optional (e.g, just saw in trunk the new 
> flash for 500 error messages, etc.)
>
> On Monday, January 14, 2013 6:39:54 PM UTC+1, Massimo Di Pierro wrote:
>>
>> 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 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.
>>
>>
>> On Sunday, 13 January 2013 23:37:55 UTC-6, weheh wrote:
>>>
>>> I upgraded to web2py 2.3.2 last week and got burned by web2py.js 
>>> breaking backwards compatibility with my component file upload. This is 
>>> probably the 3rd time this has happened to me, so shame on me for not 
>>> taking precautions. Nevertheless, I think it highlights an underlying 
>>> web2py problem.
>>>
>>> Components are my mainstream methodology and I have no plans on 
>>> returning to loading entire pages every time someone clicks a link. Problem 
>>> is, file upload is a second-class citizen to web2py components because ajax 
>>> doesn't support multi-part forms. And components without file upload are 
>>> practically useless -- sorry if that sounds harsh, but it is. So users have 
>>> to go the js upload route.
>>>
>>> This gets really when web2py.js changes, because it tends to break my 
>>> old js upload flow. Is there any way we could make js-based component file 
>>> upload work out of the box with web2py so that changes in web2py.js won't 
>>> affect it?
>>>
>>

-- 



Reply via email to