-
Posts
-
Hi guys,
I have been troubleshooting this with other developers to death and this all points to the Enfold 4.5.6 update.
It is impossible to retrieve the share count from FB if FB cannot read the page/post.
Running it by the FB debugging tool should work. Example:
Site runs Enfold 4.5.5
https://developers.facebook.com/tools/debug/og/object?q=https%3A%2F%2Fargen-travel.com%2Fthings-to-visit-in-patagonia%2F
Status: 200 OKSite runs Enfold 4.5.6
https://developers.facebook.com/tools/debug/og/object?q=https://staging-ligadejusticia.kinsta.cloud/cuando-dolores-aparecen-despues-del-accidente-carro/
Blank page (no response) It takes about a couple of hours for this to clear and allow the FB tools debugger to run properly. Any modification to the post text and post update, will produce this issue again.Same site runs Enfold 4.5.5
https://developers.facebook.com/tools/debug/og/object?q=https%3A%2F%2Fligadejusticia.com%2Fcuando-dolores-aparecen-despues-del-accidente-carro%2F
Status: 200 OKHope you get to see it asap or the error will clear up. The other option is me giving you access to the Staging site so you can modify a post and see it yourself.
This happens on all the sites that I updated to 4.5.6. Let me know if you need access.
Thank you!!
Havi.
Hey havi,
Thank you for using Enfold.
Have you tried putting the url manually back to the debug tool instead of going directly to that url? It works fine on our end.
Time Scraped
3 minutes ago
Scrape Again
Response Code 200
Fetched URL https://staging-ligadejusticia.kinsta.cloud/cuando-dolores-aparecen-despues-del-accidente-carro/
Canonical URL0 likes, shares and comments (More Info)
Based on the raw tags, we constructed the following Open Graph properties
og:url https://staging-ligadejusticia.kinsta.cloud/cuando-dolores-aparecen-despues-del-accidente-carro/
og:title Accidente de Carro: Cuando los Dolores Aparecen Después del Accidente
og:description Si las molestias y dolores aparecen después del accidente de auto, no pierdas tu derecho a compensación por lesiones personales. Sigue estos consejos.
og:image https://staging-ligadejusticia.kinsta.cloud/wp-content/uploads/2019/04/dolores-despues-del-accidente-de-carro.jpg
og:image:alt Qué hacer cuando los dolores aparecen después del accidente de carro. Abogados de accidentes y lesiones personales.Best regards,
IsmaelHi Ismael,
The caching clears in a couple of hours. You checked much later than that. I can give you access to the staging site and all you have to do is modify any post from the blog and update it and immediately check the FB debugging tool and you’ll see it in action.
You won’t get a response code at all. The FB debugging tool is unable to retrieve the page.
Let me know and I’ll be more than happy to provide you with access!
Warmly,
Havi
PS: I was hoping it would be fixed on 4.5.7 (I have another client where I already updated the theme) but no luck (actually there is some CSS that is not working as it did before that has to do with hyperlinks – I’ll add another ticket for that one) I am withholding from updating the theme for other clients and I’d rather not! Help! Thank you!Hi,
Thanks for the update.
Did you test it using another theme? I don’t really think this is an issue with Enfold. It’s probably an issue with the debugger’s cache mechanism.
Related thread: https://woorkup.com/facebook-open-graph-debugger-cache-clearing/
The solution here might help.
// https://stackoverflow.com/questions/5776567/facebook-open-graph-not-clearing-cache
Just append the “fbrefresh=” query to the url.
Best regards,
IsmaelHi Ismael!
The related thread is not exactly what’s happening here. This is not related to the thumbnail image. A blank page (no content – no FB debugging tool) is rendered when accessing the FB debugging tool. FB is unable to reach the page itself for about 2 hours after any modification to the text in the page is made (or posted for the first time)
This is how you can actually pull the shared count from FB:
https://graph.facebook.com/?id=https://ligadejusticia.com/nassau-county-taller-pequenos-negocios/&fields=og_object{engagement}
and it should not show as it does:
{
“id”: “https://ligadejusticia.com/nassau-county-taller-pequenos-negocios/”
}
This is indicative of FB not being able to reach the post. I am working with the ESSB plugin guys as well to see what may be blocking this or if it’s a FB API issue. If the latter, I am sure they will reach out to FB developers.They don’t think based on what they read on the latest Enfold changelog that anything there could have affected this but I want to hear it from you. Do you think any of the Enfold caching mechanisms or speed mechanisms could have affected this?
When I look at the Chrome developer console I see there’s a 400 error from https://graph.facebook.com/
Thank you for your continued support!!
Warmly,
Havi
Hi,
Thanks for the update.
You need an access token before you can use the graph API or access any posts info with it.
// https://developers.facebook.com/docs/graph-api/overview
// https://developers.facebook.com/docs/facebook-login/access-tokensThe debugger or scraper works fine.
// https://developers.facebook.com/tools/debug
Use the post url in the field.
Best regards,
Ismael
- You must be logged in to reply to this topic.