wp_get_attachment_url() uses the GUID as the URL

[DD32]

At present wp_get_attachment_url() relies upon the GUID for the URL of the attachment, As discussed on wp-hackers ("Re: [wp-hackers] Re: permalinks redirected despite WP_SITEURL") this shouldnt be done due to the fact that it just so happens that the guid is the url in wordpress

The attached patch attempts to use the attachment metadata to workout the files location, followed by using the filtered uploads directory to determine the real location (See comments in patch).

[DD32]

A possibly better option would be to use _wp_attached_file metadata, see the attached patch.

Also note, That in the event the metadata fails, the uploads folder is not located, or the file does not exist within the uploads folder, it fails back to using the GUID

[ryan]

Definitely needs to be done. I'll try it out.

[ryan]

Make attachment file path relative to the upload dir

[ryan]

I expanded the patch so that files are saved to attachment meta data with paths relative to upload dir rather than absolute paths. That makes it much easier to change your content dir location or move your blog to another host.

[ryan]

(In [8796]) Make attachment file path relative to the upload dir. Don't use GUID to find attachement URL. Props DD32. see #7622

[DD32]

Changeset broke image thumbnail creation. (The full path is not passed to the image creation functions)

attached patch fixes it.

[DD32]

Looks like it also broke the exif retrieval, Patch refreshed with extra change.

[ryan]

(In [8879]) Thumbnail and exif fixes from DD32. see #7622

[DD32]

WP no longer relies on the GUID for the attachment url (but falls back to it), And it seems like the bugs caused by it have been fixed up, So closing as fixed.