Also tried making it client only by removing the listener, same error.
On 9/14/06, Inge Solvoll <[EMAIL PROTECTED]> wrote:
Hi, thanks for answering!
This is a regular web app, not a portlet. I've never used portlets.
I'm pretty sure this is the only tacos component I'm using. I'll see if I
ca
Tapestry 4.0 renders a BASE tag if you use the Shell component.
There's no way to disable this...
In 4.0.1 and 4.0.2, additional parameters were added to the Shell
so that this can be controlled.
Are you sure there wasn't any tag in your :) ?
Inge Solvoll wrote:
> I discovered that the problem
I discovered that the problem isn't tacos, it's tapestry. When i rolled back
to tapestry 4.0 from tapestry 4.0.2, it worked again. My tapestry 4.0 jar
might have been patched for the bug I mentioned in the first mail...
On 9/14/06, Inge Solvoll <[EMAIL PROTECTED]> wrote:
Also tried making it cl
Hi, thanks for answering!
This is a regular web app, not a portlet. I've never used portlets.
I'm pretty sure this is the only tacos component I'm using. I'll see if I
can mount up another one to check.
Of course the javascript I'm running could be cached. But I don't think so,
IE has been rest
Does this happen in portlets?
Do other tacos components work (i.e. AjaxDirectLink) ?
Are you sure the browser doesn't load the old javascript (due to cache) ?
If nothing works, is it possible to show us the rendered html ?
Inge Solvoll wrote:
> After upgrading to tapestry 4.0.2 and tacos 4.0.0,
