Open sainformatica opened 1 year ago
Thanks for submitting a bug report, @sainformatica! I've been able to reproduce the problem using the Jetpack App version 21.7 on an Android device. I followed these steps:
og:image
, og:image:width
, og:image:height
and og:image:type
Workaround: After publishing the post, open the post edit screen in WordPress and save changes without making any changes.
I hope that the problem is solved, since the alternative solution that you give me is not good, since if I upload the content through Jetpack it is because I do not upload it through the web, because if you later have to go to the web to solve the problem it is It would be nonsense to upload the content by Jetpack, that's why you have to find a solution that can fix the compatibility.
But thanks anyway for being attentive and writing and reporting the error that I have commented
I have found the following information and the file that includes the information for you to review and to see if there is any error and you can communicate it to jetpack.
The information is in the following links.
https://jetpack.com/support/jetpack-social/troubleshooting-jetpack-social/
https://github.com/Automattic/jetpack/blob/trunk/projects/plugins/jetpack/class.jetpack.php#L269
Hi there
I’m writing because Yoast has problems with Jetpack when uploading a post with an image through Jetpack. The problem is that it does not detect in yoast-seo-meta-tag the og:image:type property nor the og:image property and it detects as if it were a post without an image, when in fact the post is accompanied by an image. But as I have commented, all this happens when an entry is uploaded to the web through the Jetpack APP.
Also comment that if I go from the web and not from the app and I update the content, the og:image and og:image:type properties are added.
Yoast version used: Version 20.2-RC3
Jetpack APP Version: Version 21.6
Jetpack plugin version: Version 11.8.4
Also comment that I have tried and consulted before writing if it was a problem with other installed plugins and it turns out that it was not, it is how I have described the problem.
The affected domain in the case is: lesnoticiesdensergialarcon.site
I hope a solution.