Platoscave

Hi Maybellyne, Thank you very much for your help with this, the solution you have suggested has worked! I really appreciate it.

@sasiddiqui, have they given you a time frame when the plugin will be available again? Is the problem some kind of security issue that we should be worried about if we’ve got the plugin installed on our sites now?

Sorry, I found a single white space at the bottom of my functions.php file that caused the error when Yoast was updated.

• This reply was modified 2 years, 3 months ago by Platoscave.

I know that you are incredibly busy, but any advice you can give on this would be greatly appreciated.

Hi again Priscilla,

Thanks for this, it makes sense and is very helpful. I appreciate all you and your teams time and help on this, I think that gives me everything I need.

Hi Michael,

Yes it works when the image is set in the Yoast SEO meta box, which is good news, but because of our workflow, we don’t want to have to use an image from the WordPress image library (ie we want to use a url to set the image from our CDN) and we want to set the image programatically. Is there a method you can suggest that will allow us to set the OG image programatically that will still allow Yoast to update the oEmbed file?

Thanks again very much for your time and help.

Thanks for the update Md,

As I pointed out in my initial post, in the Yoast documentation here: https://yoast.com/advanced-technical-seo-social-image-ogimage-tags/
It says the following:

‘Frustratingly, if there’s oembed functionality enabled on a page (as is often the case with WordPress sites), LinkedIn with often retrieve the values from that embed code. Rather than any on-page values.

This took some rather painful debugging. But we were thankfully able to fix the problem in Yoast SEO by also rewriting the oembed values to match the on-page values (or disabling / conditionally routing oembed).’

So the question I am asking is does Yoast rewrite the oembed values in the /wp-json/oembed/1.0/embed file or not? The yoast docs say that it should, and if it should, my question is why isn’t it on our site?

Thanks very much.

Hi @pcosta88,

Thank you very much for looking at this. I’m sorry for the trouble.

The site is on 5.6.2.
Yoast is on 15.9.1.

Because we want to use an image from our CDN and not from the wordpress image library, we use a custom field to set the og:image, see the following function, it was taken from here: https://gist.github.com/amboutwe/811e92b11e5277977047d44ea81ee9d4

/* Change Open Graph image URLs in Yoast SEO
 * Credit: Yoast Development team
 * Last Tested: Jul 04 2018 using Yoast SEO 7.7.3 on WordPress 4.9.6
 */
add_filter( 'wpseo_opengraph_image', 'change_opengraph_image_url' );
add_filter( 'wpseo_twitter_image', 'change_opengraph_image_url' );
function change_opengraph_image_url( $url ) {
  if (isset($GLOBALS['SOCIAL_SHARING_IMAGE'])) {
    return 'https://images.wtmfiles.com/' . $GLOBALS['SOCIAL_SHARING_IMAGE'];
  }
    return $url;
}

We are using beaver builder.

Thanks again for your time and help.

Hi Suwash,

Yes, it does appear to just be the home page.

Hi Priscilla,

Thank you very much for getting back to me so quickly, I really appreciate it. We are running the latest version of Yoast 15.9.1 and are seeing this issue.

I think you can see the issue here in the Linkedin Debugger:
https://www.linkedin.com/post-inspector/inspect/https:%2F%2Fwww.humancondition.com

The share image url is that is being set via Yoast in the og:image field is: https://images.wtmfiles.com/WTM-homepage-logo-share_WEB_1200x630.jpg
You can see that Linkedin can see this image, but has chosen to use the image from the /wp-json/oembed/1.0/embed file which is setting this image https://images.wtmfiles.com/main/The-interview-jeremy-griffith-craig-conway-desktop-1015px-no-text.jpg as the ‘thumbnail_url’.

Please let me know if you need anything further. Thank you again for your time and help.

Hi Ante,

We have checked out the code today and found that the src attribute is being set on the page load on Chrome, and the IntersectionObserver is not used.

This is the relevant snippet from the JavaScript side found in wpp.min.js:

(f.images || f.videos) && function() {
        if (e = b.querySelectorAll('[loading="lazy"]'), "loading" in HTMLImageElement.prototype) e.forEach(function(e) {
          e.src = e.dataset.src
        });
        else if ("IntersectionObserver" in a) {
          var r = new IntersectionObserver(function(e, t) {
            e.forEach(function(e) {

It enters in the first if, which sets the src attribute. On IE11 there is no loading in the prototype of the Image element, no IntersectionObserver either. Hence it falls back on the other conditions.

Currently this is broken on modern browsers like Chrome/Firefox because of the first if we mentioned.

Can you please take a look?

Okay, I have asked you about this before and you fixed it last time, so maybe it will be the same issue as last time? I am using IE 11 on Windows 10.

Thanks for your time.

Thanks very much Alaca, I really appreciate your time and help!

Thank you very much Kaspars, that worked for me. I really appreciate you taking the time to help!

Hi Application passwords, I’m still looking for a solution for this issue. Is this something that you can help with?