relative paths to og:image..

Hello,

Yes, the plugin generates metadata only for the images that are attached or embedded (only flickr is currently supported) to the post. The post is not scanned for other images that have been manually inserted into the content.

What puzzles me is why the URLs are relative. Normally, this should not be happening. The plugin uses the WP API (wp_get_attachment_image_src()) to retrieve the image URL and uses the url without any further processing. So, I assume that somehow the URL has already been stored in the database as a relative path, but I’m not really sure.

What can be done is to pass the retrieved image URL through site_url() so as to transform it to an absolute path.

I’ll do some more research about this issue within the week and post back on this topic about it.

George

On the other hand, WP may already store relative image URLs and then construct the full URL when wp_get_attachment_image_src() or wp_get_attachment_url() are used. Since these functions can be filtered, some custom code might not be letting them to return a full URL. I’m really out of ideas here… I’ll need to do some research about it within the week.

George

Thanks for letting me know about site_url().

Regarding the other issue, I’ve received another similar report, but it seems that this is an issue related to how Facebook uses the provided opengraph metadata and not to the Opengraph metadata itself. If I’m missing anything, please let me know and, if required, any issues will be fixed ASAP!

Also, I’m skeptical about making the generation of og:video meta tags an option, because I’m sure this issue will be resolved by Facebook sooner or later.

In the meantime, if you want to suppress og:video tags in opengraph metadata, you could filter the generated opengraph metadata by using the following code:

function customize_og_suppress_ogvideo( $metatags ) {
    $metatags_new = array();
    foreach ( $metatags as $metatag ) {
        if ( strpos($metatag, 'og:video') === false ) {
            $metatags_new[] = $metatag;
        }
    }
    return $metatags_new;
}
add_filter( 'amt_opengraph_metadata_head', 'customize_og_suppress_ogvideo', 10, 1 );

Please let me know if it does the trick.

Thanks in advance,
George

I’m still confused about why wp_get_attachment_image_src() returns relative paths in one of your sites. Do you use any plugins that could possibly interfere with image uploads in this particular site? Changing the uploads directory should not be a problem.

FYI, the following database queries display how the attachment links are stored in the database.

Images:

SELECT guid FROM wp_posts WHERE post_mime_type LIKE 'image%' LIMIT 10;

Audio:

SELECT guid FROM wp_posts WHERE post_mime_type LIKE 'audio%' LIMIT 10;

Video:

SELECT guid FROM wp_posts WHERE post_mime_type LIKE 'video%' LIMIT 10;

Not asking to run them. I’m just posting them for informational purposes.

I admit that I am surprised that WP stores absolute URLs int he database. So inefficient.

I also found many discussions about storing absolute or relative URLs, so I guess many web sites might be affected out there.

As I see it, the best way to resolve this issue is to create a wrapper function that checks if the returned attachment URL is relative or absolute and process it accordingly. I will need some time to make sure I have fixed all attachment URLs and that it will work as expected in all cases.

George