Thanks guys, I wondered if it might be something like that but also thought
backwards compatibility was a big thing. Guess I've got an excuse to just
update to the new layout with bootstrap too and get the look of my apps all
uniform.
On Sunday, December 16, 2012 8:37:58 AM UTC-6, Niphlod wrote:
>
> please update web2py.js to the latest version.... if you're coming from
> 1.99.4 probably the file in your app is named web2py_ajax.js .
> As soon as it is updated, it will "decode" the escaped js commands and
> flashes back to "normal".
>
> On Sunday, December 16, 2012 6:04:51 AM UTC+1, Brian M wrote:
>>
>> I'm also noticing that my response.flash is getting escaped as well, so
>> everything reads as Some%20flash%20message :(
>>
>> On Saturday, December 15, 2012 10:56:07 PM UTC-6, Brian M wrote:
>>>
>>> So I'm finally getting around to moving from web2py v1.99.4 up to trunk.
>>> Everything seems to be working pretty well except some javascript stuff
>>> within LOAD(). I've got a couple of forms pulled in by LOAD(....,
>>> ajax=True) and when submitted and processed they return instructions via
>>> response.js the problem is, suddenly those javascript commands are being
>>> escaped, so instead of
>>> $("#edit_vol_dialog").dialog("close");
>>>
>>> I'm ending up with
>>>
>>> %24%28%22%23edit_vol_dialog%22%29.dialog%28%22close%22%29%3B
>>>
>>>
>>> which results in a syntax error when the browser tries to execute the
>>> commands.
>>>
>>> Has something changed that is causing the contents of response.js to get
>>> escaped? Elsewhere I've got ajax(..., ':eval' ) calls hitting a controller
>>> that returns via response.js and those still work fine without the
>>> javascript being escaped. The only difference I can think of is that the
>>> code that works only returns response.js while the code that doesn't is
>>> also returning other html.
>>>
>>> Thanks for your help,
>>> ~Brian
>>>
>>
--
