willismorse

However in 1.5 where most of the themes have a single.php template for displaying the single post view (when clicking on the permalink) the relative path does NOT work.

Bummer, you’re right.

I’m also wondering how one goes about moving a WP site to a different location. There should be a more template-based solution for this problem, because the absolute urls are also going to break if you move WP on your server, or move it to a different domain.

The real solution for this is to have a template variable that knows where the image folder is, and can generate an absolute URL as needed at render time. I don’t know enough about the WP 1.5 architecture to know whether this is doable. I suppose all those image plugins deal with this problem.

Willis Morse

I can MySQL-change them all, but I wish I didn't have to.

That brings up my next question. I’ve now got go back relative-ize a whole ton of image links in many many entries. Any thoughts on an easy SQL (or other) way to do this kind of bulk edit?

Willis Morse

The problem with the domains is that the domain forwarding is being done by NetworkSolutions. I’m not using rewrite rules in Apache to do this. My Apache server never sees anything about the virtual domain, it just gets an URL into the actual domain. This forwarding is a service that NetworkSolutions just starting offering, so it may become an issue for more users.

I tried an experiment and hand modified the image links in one entry to be relative URLs. Everyone that couldn’t see them before can see them now. So the domain conflict oes seem to be the problem.

When I click on the entry title (permanant link), the relative image URLs still resolve properly, because it’s still just index.php. Is this behavior going to be different in 1.5? I’m still using 1.2.

Thanks for the replies,
Willis Morse

Thanks for the reply. So is the official wordpress project going to support multiple blogs?
Thanks,
Willis Morse

What about the MuWordpress project:
mu.www.remarpro.com
Does that have anything to do with this main WordPress project, or is it an independant code fork? The mu project site duplicates the dev blog from this site, and offers a download of version 1.3. So it’s a little unclear what the relationship is.