Re: Too many path parts in page parameters

2009-07-04 Thread Daniele Dellafiore
hi. I have not tried yet cause is not high priority form me now, but as long as Igor is right, I expect that the Strategy does not play well with non absolute URL so you can just change the img src URL. On Fri, Jul 3, 2009 at 9:19 AM, Bas Vroling wrote: > After removing all the highslide code, th

Re: Too many path parts in page parameters

2009-07-03 Thread Bas Vroling
After removing all the highslide code, that is not the only thing that goes wrong. In my html file I have a panel containing this: Data the mixedParamUrlCodingStrategy trips on that too, and I can't see why this doesn't work... On 2 Jul, at 17:54, Igor Vaynberg wrote: your highslide js

Re: Too many path parts in page parameters

2009-07-02 Thread Igor Vaynberg
your highslide js is making those requests, you may have to change it to request images via absolute urls -igor On Thu, Jul 2, 2009 at 7:22 AM, Bas Vroling wrote: > I ran the debugger, and the urlPath the mixedParamUrlCodingStrategy gets > served is "/img/info01.gif", which does not make sense. T

Re: Too many path parts in page parameters

2009-07-02 Thread Bas Vroling
I ran the debugger, and the urlPath the mixedParamUrlCodingStrategy gets served is "/img/info01.gif", which does not make sense. This is just an image and nowhere is there a request to open up a new page... After that, it goes to parse "/highslide/graphics/outlines/rounded- white.png" , then

Re: Too many path parts in page parameters

2009-07-02 Thread Daniele Dellafiore
as you can see I posted a similar issue. you can start debugging the strategy to see the values of parameters. On Thu, Jul 2, 2009 at 10:36 AM, Bas Vroling wrote: > I have a page which takes one parameter ('id') and build itself from there. > In the debugger it shows that only one parameter is pa