The only thing coming to mind is "add" a
web2py-component-flash-international header in "new trunk" and check only
that in new web2py.js, leaving web2py-component-flash header the way it was
before.
Il giorno martedì 5 giugno 2012 22:17:36 UTC+2, Massimo Di Pierro ha
scritto:
>
> We cannot do that.
>
> Yet I agree that this improvement broke backward compatibility and needs
> to be reverted until we find a way to deal with intrnationalization of
> flash and in a backward compatible way.
>
>
>
> On Tuesday, 5 June 2012 15:02:07 UTC-5, Niphlod wrote:
>>
>> Hi, I'm all for supporting international flash messages, but for
>> applications relying on the old web2py.js (or even web2py_ajax.js) the
>> message appear urlencoded.
>>
>> That's because
>>
>> *var
>> flash=**decodeURIComponent(**xhr.getResponseHeader('web2py-component-flash'**)**);
>>
>> *expects an encoded flash message (done in main.py in trunk) but if it isn't
>> (encoded, e.g. using the 1.99.7 version)
>> the old line transforming web2py-component-flash header gets the "raw"
>> urlencoded message.... i.e. shows "form%20accepted"
>> instead of "form accepted".
>>
>> Maybe a message stating that web2py.js or web2py_ajax.js of old apps needs
>> to be overwritten by the one in welcome
>> for web2py 2.0.0 will prevent angry users :P
>>
>>
>>
>>
>>
