Thread Starter
jenja
(@jenja)
Hi,
I continued testing and found out that when I visit the facebook debugger for each article and press “Fetch new scrap information” for each article the right description is shown.
Without that it doesn’t work. Due to the error messages I received in the facebook debugger I checked different options, what to fill in under the WP Meta Settings under the Facebook profile URL. When filling in the URL I receive the error message
Object at URL ‘http://www.myclientssite.td’ of type ‘website’ is invalid because the given value ‘https://www.facebook.com/myclientsfacebooksite’ for property ‘fb:admins’ could not be parsed as type ‘fbid’.
When entering the facebook site id I receive the same error message. When entering my personal facebook id into the URL field the error message disappears and I only receive warnings, but I still have to to the “fetch new scrap information” thing again for each single article.
The warnings are
The ‘og:url’ property should be explicitly provided, even if a value can be inferred from other tags.
and
fb:app_id hasn’t been included in the meta tags. Specify the app ID so that stories shared to Facebook will be properly attributed to the app. Alternatively, app_id can be set in url when open the share dialog. Otherwise, the default app id( 966242223397117 ) will be assigned.
Is there any option to avoid this complicated procedure?
Kind regards
jenja
Thread Starter
jenja
(@jenja)
a bit later:
I found out that for new articles I don’t have to run through the debugging prodecure.
There is only one question left: in the facebook debugger I receive the warning:
The ‘og:url’ property should be explicitly provided, even if a value can be inferred from other tags.
Does someone know where to add this?
Kind regards
jenja
Hi,
Sorry for the late reply (holiday time this week :).
We’ll check that on monday and maybe provide a fix in the next version if we can reproduce that. Otherwise I’ll ask for more information.
Cheers!
Hi,
This Facebook SEO content sharing problem has been fixed in the latest version, the 1.7.3.
Cheers,