OK, that did the trick. Thanks.
As for the web2py_ajax.html file, all I have to say is, 'Urggh!' This
is probably the 3rd time I've been bitten by changes to the file in
the last year or two. Must keep that in mind in the future.
Again, many thanks for the help, Nathan. You too, Jonathan.
On Dec 4, 5:26 pm, "mr.freeze" <nat...@freezable.com> wrote:
> Yep, changed on 11/3. Maybe web2py_ajax.html doesn't fall under the
> same backwards compatibility umbrella as the actual framework. Anyway,
> it's selecting by name so just change your onclick to:
> _onclick="ajax('process_checkbox',['junk'],':eval');")
> ...and it should work.
>
> On Dec 4, 4:17 pm, "mr.freeze" <nat...@freezable.com> wrote:
>
> > Perhaps this was a recent change in trunk but it's definitely not
> > backwards compatible. Selecting by name and id will definitely give
> > you different results.
>
> > On Dec 4, 4:14 pm, "mr.freeze" <nat...@freezable.com> wrote:
>
> > > Your web2py_ajax.html ajax function IS different. Note this line:
> > > Yours:
> > > q = jQuery("[name="+s[i]+"]").serialize();
> > > Standard:
> > > q = jQuery("#"+s[i]).serialize();
>
> > > On Dec 4, 3:32 pm, weheh <richard_gor...@verizon.net> wrote:
>
> > > > On close inspection, web2py_ajax.html is out of date on my test app. I
> > > > updated web2py_ajax.html and the test case still doesn't work.
>
>
