W3 Total Cache caused isssue with og:image (image thumbnail when posting to FB)

I want to add that I also took a look at this post:
https://wordpress.stackexchange.com/questions/53630/w3-cache-plugin-and-facebook-sharing
And applied this solution but there is no change in the result:
Go to the W3 Cache plugin settings, more specifically to “page cache” and make sure to reject these user agents:

facebookexternalhit

FacebookExternalHit/1.1

FacebookExternalHit/1.0

Hello @huynhtuanstb,

I am sorry to hear you are having issues when posting to FB but I am happy to help.
Is there any other caching solution that you are using besides W3 Total Cache.
Can you also please disable W3 Total Cache settings one by one in Performance>General settings, save and purge the cache after each disables See which setting is causing this issue.

Happy to see your response.
I tested as your request and found that the Page cache is the key reason for such problem.
If turnning off page caching function in this plugin, everything relating to open graph seems to be okay. I tested by Facebook object debug.
Also, I configured W3 Total Cache as guidance by this post
https://stylemixthemes.com/wp/guide-to-w3-total-cache/
I use W3 Total Cache and Cloudfare.
Thank you for your support, hope to see further guidance!

• This reply was modified 5 years, 4 months ago by huynhtuanstb.

Hello @huynhtuanstb,
I’ve spoken with the team, we tested this and it parses well.
Based on the answers you received in the links you provided, there’s something wrong with server configuration.
In order to investigate this further, I can offer you our Pro support in Performance>Support.

thanks!I’ve submitted a bug report in your Pro support!

I think I should repost this here for other users to see what I finally received after following all your suggests above.
“You are a supporter or that guy!! I think that guy even provided me more insight to find out problem than you.
You should remember that I inspected step by step by deactivating all relavant plugins and found that your W3TC caused a hurt to social meta tab that Facebook can not get information my server sends to them.
And I also step by step disabled and enabled functions of W3TC and found that cache page is the key cause of the problem. I informed it to you with hopes that (1) other users can get this bug and (2) you looked into it to fixed in next version or right now or give guidance to configure the cache page to avoid that problem.
But not, you talk around and claim for my server reason and tell me give you money for more support!
I use your plugin function that you have it free, and it causes something wrong, why I have to pay money.
Not any upgrading function here!
Thanks for your plugin, it works well in increasing speed but still has something should be considered and to be improved!”

Hello,
I replied to you via email and I’ll post here as well.

After you posted the topic and described your issue, I’ve consulted with the team of developers and we’ve run some tests to see if this is the issue on our end. After we performed testing there were no issues and it parsed as expected, so we confirmed that this is not a W3 Total Cache issue. We do things thoroughly, so I can assure you that we checked every possibility before offering you the Professional support.

That being said and after checking out the responses on the links you provided, we think that the issue is with your server configuration, and I offered you our Professional support to investigate this for you. To do that, you need to purchase our solution and the developer will investigate this for you and this takes time. Once again, we failed to replicate the issue you are having and everything is working as expected on our end. The optimal W3 Total Cache configuration takes into account several factors: your theme, your plugins, and the technologies available on the server. If you can investigate this on your own that is fine too.

I am not going around on the forum and offering our paid support. The support is free, of course, but in cases such as yours, we need to investigate this deeper.