WPSSO Warnings – Jetpack?

Resolved inetinitiatives.com
(@inetinitiativescom)

10 years, 11 months ago

Hello,

First of all, thank you for your plug-in – it solved our issues with identifying exactly what image we wanted associated with our shared posts.

However I’m getting warnings on posts (WPSSO Warning: Possible conflict detected – your theme or another plugin is adding a meta property=”og:image” HTML tag to the head section of this webpage.) among others ever since the updates of April 21.

I’m using JetPack Publicize for my social connections and also All In One SEO; I have All In One’s social connector disabled and JetPack says that they fall back when another plug-in’s OG tags are detected.

My theme hasn’t updated just the WordPress core and associated plug-ins during the April critical security update.

When I run the FB Open Graph object debugger I’m seeing the correct image under “When shared, this is what will be included” but I’m also seeing the duplicate tags.

How can I go about detecting where these additional tags are coming from?

https://wordpress.org/plugins/wpsso/

Viewing 6 replies - 1 through 6 (of 6 total)

Thread Starter inetinitiatives.com
(@inetinitiativescom)

10 years, 11 months ago

Oh I forgot to mention, even though there are meta properties for og:image content, which include the URL and height and width, no og:image property is included for the section saying “Based on the raw tags, we constructed the following Open Graph properties”.

Plugin Author JS Morisset
(@jsmoriss)

10 years, 11 months ago

I would need a permalink URL to an example post/page. 😉

Thanks,

js.

Thread Starter inetinitiatives.com
(@inetinitiativescom)

10 years, 11 months ago

http://www.findingwoo.com/inspiration/whos-running-with-you/

I think you may already be helping me on the WPSSO forum, but a duplicate response here might help others in the future.

Plugin Author JS Morisset
(@jsmoriss)

10 years, 11 months ago

It looks like the Facebook cache had old information in it. See this FAQ for more info: http://surniaulula.com/codex/plugins/wpsso/faq/why-doesnt-facebook-show-the-correct-image/

The Facebook debugger looks fine now: https://developers.facebook.com/tools/debug/og/object?q=http://www.findingwoo.com/inspiration/whos-running-with-you/ (after refreshing its cache)

As for the duplicate tags, the webpage header section looks fine now. My guess would be that you use a caching plugin/service that does not flush it’s cache properly when a post/page is updated (W3TC maybe? It’s well known for its numerous bugs). Since the meta tags look fine now, I would guess the content has expired and the duplicate tag warnings have probably disappeared.

js.

Thread Starter inetinitiatives.com
(@inetinitiativescom)

10 years, 11 months ago

Hi there,

That’s great that the errors are now gone… but I don’t use a caching plugin, which makes this weird. Also, I’m confused (sorry for my ignorance) about flushing the Facebook cache – I though this occurred each time the Object Debugger was launched? Is there a step for manually flushing the cache that I’m missing?

I’m afraid that there may still be a problem here and won’t be able to verify if the problem is fixed until one of our next scheduled posts is posted to FB (and either takes the image correctly or posts a blank). If you look at the attachment, the debugger ‘sees’ the image in the OG properties based on the raw tags, but the “When shared, this is what will be included” space is empty (and this wasn’t occurring before). I’d feel a lot more confident that the situation was resolved if I could see it here.

Thank you for your help.

Plugin Author JS Morisset
(@jsmoriss)

10 years, 11 months ago

You have to click the “Fetch new scrape information” button several times for Facebook to refresh its cache and show you results based on that refreshed cache.

js.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘WPSSO Warnings – Jetpack?’ is closed to new replies.