ashleynexvelsolutions

Same issue here. Please keep us posted when the new version comes out.

@lmceo Might be the same issue I was having, which was resolved in the latest plugin release. https://www.ads-software.com/support/topic/images-are-lazy-loading-when-they-shouldnt-be/

@robosoft Yup, that did it. Thanks.

@marionha Thank you

@robosoft Just checking in to see what the status of this is since it’s been nearly 4 days and I haven’t heard anything.

@cocagneolivier No you’re not the only one. I’m having the same issue https://www.ads-software.com/support/topic/images-are-lazy-loading-when-they-shouldnt-be/ and so is this other person https://www.ads-software.com/support/topic/infinite-scrolling-16/. But this thread here seems to be marked “resolved” so the plugin author may not be getting notified of the replies below robosoft. I don’t know if you’ve got a way on your end, because you’re the thread starter, to mark it unresolved or not.

It appears to be working as expected for me. Thank you! @sasiddiqui

Well that’s strange. Now I’m back to having the error all the time, no matter if there’s something in Site Address or not.

1. There’s the screenshot: https://paste.pics/875264e9015cf89b9f28a0ac441782ab. When I hit “Copy Error” and paste it into my text editor this is what it says:

TypeError: Cannot read property 'toLowerCase' of undefined
    at o.value (https://backend-gatsby.mmklawfirm.com/wp-content/plugins/wordpress-seo/js/dist/externals/socialMetadataForms-1670.js:1:11100)
    at Ie (https://backend-gatsby.mmklawfirm.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:104:8)
    at rh (https://backend-gatsby.mmklawfirm.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:103:334)
    at zj (https://backend-gatsby.mmklawfirm.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:228:490)
    at Th (https://backend-gatsby.mmklawfirm.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:223)
    at tj (https://backend-gatsby.mmklawfirm.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:152)
    at Te (https://backend-gatsby.mmklawfirm.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:146:151)
    at https://backend-gatsby.mmklawfirm.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:61:68
    at unstable_runWithPriority (https://backend-gatsby.mmklawfirm.com/wp-includes/js/dist/vendor/react.min.js?ver=16.13.1:25:260)
    at Da (https://backend-gatsby.mmklawfirm.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:60:280)

2. I’m using Gutenberg on that site.

3. They’re the same. Settings > General screenshot: https://paste.pics/12e692af96cda389edd3c92867eb5313. The plugin’s settings screenshot: https://paste.pics/f981afd30294b75d1dad227518970eff

OK I changed it to something different https://paste.pics/be054b1842b3c9ce62736c36520f1f91 and post editing came back after I did that https://paste.pics/48add79249c2b77219b7cc6c093ee16d. But of course that’s not really correct. When I either have the Site Address matching site_url() or when I leave that field blank the error occurs.

@sasiddiqui

I think I’m having the same issue. I updated to version 1.2.0. When there’s something in Site Address in the plugin’s settings I don’t seem to have the issue editing posts. It’s only when that field is left blank. @sasiddiqui

Aha! That helped me narrow it down to the theme. It’s just a Gatsby site so there’s nothing on the front end of https://wordpress-321502-1296134.cloudwaysapps.com/, so my WordPress theme is extremely bare bones. In functions.php it was missing add_theme_support( ‘title-tag’ );. So it’s working now. Thank you @pcosta88 and @priscillamc.

Looking at your docs here https://developer.yoast.com/customization/apis/rest-api an example would be https://wordpress-321502-1296134.cloudwaysapps.com/wp-json/yoast/v1/get_head?url=https://wordpress-321502-1296134.cloudwaysapps.com/hvac-services/. It’s got the og:title but not the <title> tag. I have just disabled all other plugins to see if perhaps it was a plugin conflict, but that did not do anything.

I have to get back to you about how it’s being pulled in to GraphQL.

Hey Priscilla,
Thanks so much for getting back to me so quickly. I was able to find what I needed here: https://gist.github.com/amboutwe/0c71e42aa164238007d7ea88f174a93f.

I’m using WordPress in a headless manner. I do wonder why yoast_meta in graphql doesn’t output a <title> tag. On a traditional WordPress site your plugin outputs that. In yoast_meta graphql it’s only giving me the og:title. Your documentation on the REST API https://developer.yoast.com/customization/apis/rest-api implies that it’s supposed to be there.

“The head contains the complete meta output for the page. This means the Yoast SEO REST API output contains everything:

The title
…
OpenGraph meta data
“

Yeah, that was it. Sorry about that.

Oh. Wait a minute. It might help if I had the most recent version of the plugin installed. Looks like I’m on version 3.0.1.

Hello? Anybody?