Quote from: rthrash at Nov 30, 2005, 02:15 PM
I’m not so certain that the image path rewriting is not in fact hard coded to the place when you hit the save button. Not certain, but I’ve never used it for that exact reason. Guess we’ll have a pretty good test case of that soon!
Ok heres the update to what happened. I’ll use image.gif as an example
Using base_url or site_url worked fine from the front end.
base_url added
before the /assests/images/image.gif. After I added <base href="[(site_url)]" /> in template, it showed /assests/images/image.gif
site_url looked like
http://domain.com/assests/images/image.gif
What I did discover is that the image was not visible from the backend (or quickedit) when edit the page with a WYSIWYG editor as it wasn’t able to evaluate the variables.
I would like to suggest that this is improved, although it didn’t affect the web users, I still had to update every image on the site so the editors could see the image when using a WYSIWYG editor, defeating the advantage of using the variable in the first place.
When images were added using thew WSIWYG editor and not using variables they were given the old URL of the development site and therefore didn’t work when moved to the new site.
FYI image links without http:// also aren’t shown in the WYSIWYG editor