On my project, we extended the pull tool (we were using $content instead of $ui) to render the correct link which is, in our case "/images/image.jpg". This way we are able to keep the control to do things like point all image requests to a different server if we like without needing to change the code.

-B

On Tuesday, September 9, 2003, at 01:15 PM, Runako Godfrey wrote:

I have seen this in both Turbine 2.2 and Turbine 2.3, running against
Tomcat 4.1.x (I think 4.1.27). I couldn't get it working easily,
probably due to a configuration error on my part. Nonetheless, I found
it easier to just point directly at the images (e.g. by putting the
images in /images and using img src="/images/image.jpg") and not use the
UI tool.


Runako

-----Original Message-----
From: Eric Emminger [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 1:51 PM
To: Turbine Users List; [EMAIL PROTECTED]
Subject: Re: localhost, even from another machine.


Matthew


Matthew Pomar wrote:
When Turbine creates the image URLs using $ui.image($ui.spacer) it
includes the full path including the "localhost" server. It
does this
even when the site is accessed from another machine, which
causes the
images to be broken.

Is there a way around this?

Are you connecting directly to Tomcat? Which Turbine and Tomcat releases?

Eric


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to