You're right.  The example I gave isn't holding up anymore!  (I swear,
I didn't change my code since my last post!) I'm getting tickets in
firebug for f3() not being defined - which makes sense.  (Btw, I find
it easier to click the most recent ticket from the "error" menu in a
pre-existing ticket tab - rather than cutting and pasting from
firebug.)

I think it may be related to some other odd behavior I can't figure
out:  I keep on having to redefine the first argument of my ajax()
functions as 'project/default/function' sometimes, and other times
just 'function.'  It seems random.

I'll post back when I can either duplicate the scenario I described
above or figure out what's going on with the ajax() URL root..

On Mar 13, 11:50 pm, mdipierro <[email protected]> wrote:
> If your callback bg_function is being called by the client it should
> show in firebug. If you click on it it will tell you the response. If
> there was a web2py error, the response will contain a ticket url. Cut
> and paste the ticket url in the browser and you will see the error.
>
> Anyway, if your callback returns a dict you should have a custom view
> else you get the generic one and I doubt that is what you want because
> it includes layout.
>
> Massimo
>
> On Mar 13, 11:19 pm, snfctech <[email protected]> wrote:
>
> > So I use firebug for most of my ajax debugging, but given the scenario
> > where your ajax bg_function returns a dictionary to a template that is
> > lacking one of the dictionary's keywords, firebug tells you nothing
> > and there are no server tickets.  You've just got broken functionality
> > suddenly and have to go back and remember e.g. that your ajax call
> > depended on a function that's now broken, and so on.
>
> > Like this:
>
> > onclick=ajax('bg_function',['source_id'],'target_id')
>
> > def bg_function():
> >     return dict(k1=f1(), k2=f2(), k3=f3(), k4=f4(), k5=f5())
>
> > # whoops!
> > # def f3(): return 'somestuff'
>
> > I don't like it when stuff doesn't work and I don't see error
> > messages.  Any thoughts on how to avoid errorless ajax bugs like this?

-- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en.

Reply via email to