Mystery solved.  In one part of the application the user is allowed to
enter a URL for the image in a form field.  The url entered was simply
"foo", and the data view simply interpreted that as local relative
url, which happens to be hanging off the current URL.

I think I need to write a validator for the input to require fully
qualified paths for that input ("http://"; prefix is required).

Yarek

On Feb 3, 2:24 pm, Yarek Kowalik <[email protected]> wrote:
> Great tips.
>
> I've know why the dialog is not repaining, but I don't know the root
> cause yet. I've discovered that there is an extra request generated
> that's causing the problem -- update-dialog-on-request was being
> called, but (refresh-request-p) is returning nil because the last
> client request is this one:
>
> http://phoenix:8080/my-app/menu/foo
>
> Problem is I have no idea where "foo" part of the URL is coming from.
>
> I don't have 'foo' anywhere in my code base, not really in weblocks
> either, except as part of the descriptive text.  It's a real mystery.
>
> Yarek
>
> On Feb 3, 1:43 am, "Leslie P. Polzer" <[email protected]>
> wrote:
>
> > > So I'm trying to debug that, but not sure where to start looking at
> > > the client side. On the server side I know that update-dialog-on-
> > > request in dialog.lisp is not getting called, so I'm guessing
> > > something on the client isn't functioning.
>
> > Check the whole chain:
>
> >   1) what the client sends
>
> >   2) what happens on the server side (trace multiple functions that
> >      you expect to be called)
>
> >   3) what the client gets back
>
> > Steps (1) and (3) with Firebug's Net/XHR functionality
> > and probably a modified weblocks.js that displays an
> > error message when a script eval failed.
>
> > That's how I would solve it (and how I solved all dialog problems
> > in the past).
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"weblocks" 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/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to