I think I'd prefer to see the checking for external redirects in the redirect()
function itself.
Perhaps on a redirect() to an external page the user should be taken to a
warning page that they are about to exit the web2py site, and ask them if
they're sure they want to continue.
This could
Hey,
Just wanted to say that I also ran into a situation recently where it would
have been nice to insert a model before db.py, and I wished it was possible.
Would be nice to allow 0_plugin_name folders as well.
This communication, including any attachments, does not necessarily represent
Sounds like you're looking for response.json
def test():
coords = ((1,2), (3,4), (5,6))
return response.json(coords=coords)
Returns a javascript array formatted like: [[1, 2], [3, 4], [5, 6]]
Or you can use response.json(dict(coords=coords)) to get a javascript object:
{coords: [[1,
will give some thought to it and this should be
probably be made the default web2py behavior. Any objection?
On Nov 25, 4:49 pm, Josh Jaques jjaq...@seccuris.com wrote:
Hey guys,
I looked into this a little more.
The problem seems to be that self.custom.begin and self.custom.end are
computed
in the
testing I've done.
Josh Jaques
Intern
From: web2py@googlegroups.com [mailto:web...@googlegroups.com] On Behalf Of
Josh Jaques
Sent: Tuesday, November 23, 2010 10:35 AM
To: web2py@googlegroups.com
Subject: [web2py] Possible BUG: Hidden fields in SQLFORM with custom render
template
Rendering SQLFORMs
If you load a form onto a web2py page via AJAX, it doesn't get the enhancements
from web2py_ajax_init().
I've included a modified web2py_ajax_init that accepts an optional parent
selector to provide some scope to web2py_ajax_init. In this way if you load a
form onto a page, you can call
Of
mdipierro
Sent: Wednesday, November 24, 2010 12:51 PM
To: web2py-users
Subject: [web2py] Re: targeted web2py_ajax_init for dynamically inserted forms
tell us more about jquery live. What do you propose?
On Nov 24, 11:44 am, Josh Jaques jjaq...@seccuris.com wrote:
If you load a form onto a web2py page via
Rendering SQLFORMs with a custom template, any hidden fields I create, as well
as the hidden ID field are not displayed in the form until a call to accepts.
I think this might be a bug because the same form rendered without a custom
template will have the ID and hidden fields without calling
, the patch will default to prefer. In
this way I believe the patch is backward compatible.
Regards,
Josh Jaques
This communication, including any attachments, does not necessarily represent
official policy of Seccuris Inc.
Please see http://www.seccuris.com/Contact-PrivacyPolicy.htm for further
9 matches
Mail list logo