arbpen

@tempopreghiera – Since you are using two different servers and one works and the other doesn’t, I would look to see which version of PHP the server that doesn’t work is using. If I recall correctly, the error you are getting is due to the PHP upgrade. The lastest stable version is 8.2. Check with your host Also, make sure that both are using the same version of WordPress and both are using the same version of the plugin. Good luck!

I don’t know what happened over the weekend, maybe it was Hurricane Hillary, but the alt text is now appearing.

Thank you, @ghernkadence for your response.

Thank you so much for fixing this. Your update must have come right after I went to bed last night. I just ran updates on the sites that I manage, and they are all fine. Again, thank you for the quick response.

Thank you!

It turned out to be the CDN that was doing it. I have CDN through a hosting provider and they have now turned off the conversion from JPG to WEBP. Then, this morning, I realized that Jetpack’s CDN was also doing it, so I turned off the image CDN through Jetpack, cleared the cache at the host, and the post went through flawlessly.

Very interesting! The mystery just got a lot larger. When I do pictures, my process is to take the image from my phone (jpg), resize and enhance it with my ancient image editor which is so old it was created before Google was even a thought (but it’s still a good editor,), convert the image and add a watermark to webp, then upload both the jpg and the webp to the server, add them to the Media Library via Add from Server, add alt via Media Assitant, then choose which jpg for the post. I already know that webp won’t work for posting to Pinterest and other apps, so my Featured Image is always jpg. As you can see from my convoluted method, that jpg I get from my phone never was or becomes a webp. That must mean that my web host is doing this – shame on them! –> … runs off to web host.

You would THINK, since it’s Google’s My Business and since Google INVENTED webp that they would accept it. Thanks for all your help. I’ll be back when I find out what’s going on. The solution to this might be helpful to someone else.

Me, too. This is such a great block, and I really need it to finish a post. Any news about when the fix is coming? Inquiring minds want to know.

It must be a bug because I am also seeing this for a post I wrote two weeks ago which is scheduled for Friday, July 15th. Two weeks ago, I was not receiving this message. The plugin is also reporting that my meta description for that post is 157 characters when it is in fact 141 characters, an acceptable length. I have premium and I’m going to report it over there, too, but I thought others should know you’re not crazy – Yoast is broken.

Thank you @georgdem for your response. I was having this problem with another plugin and your solution fixed it. I’m heading over to SVG Support now and reporting over there, too.

Brecht, it’s good to know I’m not the only person up in the middle of the night (California here). I’m using YouTube’s own embed link. https://youtu.be/cYpOg0gL6BA. Should I be using something else?

Don’t you just love the way this topic was closed only 6 days later as resolved? It is most definitely not resolved. I am also having a similar problem and deactivated the Ezoic plugin. In talks with Ezoic, they have said they are trying to work with Google’s web story team to resolve the issue. So, yeah, it’s not resolved.

You know what? Instead of marking something resolved, when others have described the issue, why not find out what might be wrong on your end, Google? Marking something resolved doesn’t do anything but artificially increase your solve numbers.

This would be the same thing as a doctor putting in a faulty heart valve and finding out the patient was sick afterward. Sure, the doctor can remove the heart valve, mark it resolved and go home. However, other doctors and patients wouldn’t be aware not to use that heart valve and people could die – and doctors and hospitals would get sued. Isn’t it better for the manufacturer to repair the faulty units?

Thankfully, no one is going to die from this Google web stories plugin being incompatible with the Ezoic plugin, but that doesn’t mean the issue should be marked resolved – fix it!

Thank you! I was also having the same problem, and now with the new unpublished update, everything is hunky-dory again. Maybe publish this update now?

Ticket #4564639 has been opened. Thank you for your help and wishing you and yours Happy Winter Holidays.

Is it possible the plugin is having a heart attack because there is already another WooCommerce Amazon Pay at another website? We are moving the store from https://healwithin.com to https://store.lizaboubari.com because of branding and server load.

Sorry I didn’t get back to this earlier. It’s been a very busy week. FWIW, when I set up the Amazon Pay plugin, I did log out of all Amazon accounts, cleared cache, etc.

Please understand that I’m using Yoast on other sites, including https://lizaboubari.com which does NOT have a premium subscription. I shall post another thread so it does NOT get marked Resolved. I’m sure that I’m not the only one with this question.