tracked in http://code.google.com/p/web2py/issues/detail?id=284
On Fri, Jun 3, 2011 at 1:44 AM, ron_m ron.mco...@gmail.com wrote:
I figured out the problem. The Javascript generated looks like this:
web2py_trap_form('('/app/default/testajax.load',)','c831268503949');
which is illegal
fixed. there was an unwanted comma in the code.
On Jun 3, 3:16 am, Sebastian E. Ovide sebastian.ov...@gmail.com
wrote:
tracked inhttp://code.google.com/p/web2py/issues/detail?id=284
On Fri, Jun 3, 2011 at 1:44 AM, ron_m ron.mco...@gmail.com wrote:
I figured out the problem. The
Verified fixed in 1.96.2
I figured out the problem. The Javascript generated looks like this:
web2py_trap_form('('/app/default/testajax.load',)','c831268503949');
which is illegal because the single quotes around the URL terminate the
single quotes of the first parameter for web2py_trap_form
It looks like a string '('
yes, I like that
keep the current release model and add some kind of Super Stable branch
which is a X months old web2py without latest features but virtually bugs
free
On Wed, Jun 1, 2011 at 2:49 AM, pbreit pbreitenb...@gmail.com wrote:
I'm pretty comfortable with the current pace. I
Hi cfh
I agree with you and I believe in the community. So any time that I can I
give my small contribution to different communities (web2py is one of them).
At the same time I believe that the main reason because web2py is not so
commercially popular as Django o RoR (just have a look to any job
I kind of understand but realistically I think Web2py users have to
recognize where the framework is at. It is still being iterated on at a very
rapid pace. If you need stability, stay on an previous version. If you run
into problems with esoteric features, don't use them or try to fix them
On Tuesday, May 31, 2011 1:33:34 PM UTC-7, sebastian wrote:
Hi cfh
I agree with you and I believe in the community. So any time that I can I
give my small contribution to different communities (web2py is one of them).
At the same time I believe that the main reason because web2py is not
I'm pretty comfortable with the current pace. I think the next logical bit
of progress would be to have two branches: 1) the current trunk and 2) the
current 1.xx.x releases with critical bug fixes.
No, I'm not using trunk. We are using web2py as a stable and robust
enterprise framework and I'm sure that you would understand that it goes out
of our budget to invest in maintaining the same framework which aim is to
save us money.
I'll wait patiently to the next stable version
Thanks
On Sun,
Sebastian,
I agree with your views completely! i *never* use anything but stable
releases with my clients, but sometimes when i have issues i get help and
fixes from the maintainers much more quickly if i can test their fixes in
trunk. Help us out (if you can) and confirm that the fix is in
If you are not using trunk, can you try trunk?
On May 28, 3:25 pm, Sebastian E. Ovide sebastian.ov...@gmail.com
wrote:
Hi All,
I'm trying to use the ajax_trap funcs. but I'm getting JS errors and
therefore the traps are not working meither for the forms nor for the links:
In firebug I'm
12 matches
Mail list logo
