Robert Reiser

@yvsso2023: I am using CF7 in combination with Contact Form 7 Image Captcha (which does not violate GDPR) and Honeypot for Contact Form 7, like you. This helps against spam bots, but manually entered spam messages still come through from time to time. I learned to live with this situation.

Thank you Jeroen.

I will see if it is possible to disable Gutenberg on my production site.

Cheers, Robert

Hi Jeroen,

the issue described in Github is exacly what I have experienced. In one of the affected posts, I did remove the featured image and the post was editable immediately, even with the latest versions of Gutenberg and WordPress SEO.

Is there anything else I can do to help?

Cheers, Robert

Hi Jeroen,

thanks for the quick reply and the suggestions. I have a local development VM where I tried things out. Here are my findings:

– The theme I am using for my production site is written by myself, based on _s.
– For testing purposes, I have switched to TwentyTwenty
– I do receive the same error message when I try to edit my post
– As soon as I disable WordPress SEO or downgrade Gutenberg, the error message disappears and I can edit my post normally.

So at this point I believe we can conclude this is not theme related. I did some further tests by trying to edit additional posts: The error message in my initial post is thrown only for *some* posts, but not for all. Some posts I can edit normally, some throw the error message. So it looks like the error is related to the *content* of the post?

I can extract data from the database, if that helps. One of the affected posts is a very small test post. Let me know if this would help you or what else I can do to help with the investigation.

Cheers, Robert

Awesome, thank you for the quick implementation!

Hello Stefan,

thanks for getting back to me – indeed I am using the MLA plugin, and I will make them aware of this as well.

Thanks for the response,

Robert

Have you disabled the REST API? I had the same issue. Re-enabling the REST API did resolve the issue.

And thanks to you guys for always considering user input.

Kind regards,

Robert

Alex, for me it would work either way and I would be happy about either implementation.

Like I said, I thought that adding the glossy option to the existing lossless and lossy re-compress options would be a lot easier than implementing something that you might not have a lot of usecases for.

Kind regards,

Robert

Sometimes I am replacing images using the Enable Media Replace plugin ( https://www.ads-software.com/plugins/enable-media-replace/ ) to change the featured image for specific posts without having to delete and re-upload an image. This way I don’t have to go to individual posts and re-select the featured image.

I found that after replacing the media using the plugin above, the images are no longer optimized by ShortPixel, which is expected behavior. But since the option already exists to re-compress an image lossless or lossy, I thought it should be easy to add the glossy option as well.

Updated from version 3.0.7 to 3.1.3 with no errors. Thank you for the quick fix.

After reviewing my nginx configuration, I found an entry which blocked access to /wp-json/ on my server, probably for security purposes. Removing this entry and restarting the server solved the issue with the counter for me.

Thanks for your help, I consider this issue resolved.

I did test version 5.0.2 the moment it was released and it did not fix the issue for me. I have tested it again with three browsers, with the same result.

Currently I don’t have a GitHub account, but I might look into it.

Sure – I deactivated all plugins except Yoast 5.0.1 and switched the theme to the latest version of Twenty Seventeen.

In Firefox, I don’t see any error message in the console, but there is also no progress in the progress bar (stuck at “Text 0 of xx processed”). I left the page open for more than 10 minutes.

In MS Edge I receive the following error message;

SCRIPT7002: XMLHttpRequest: Network Error 0x2eff, Could not complete the operation due to error 00002eff.

Chrome still shows the same error message as reported above.

Anything else I can try to help get this fixed?

Cheers, Robert

Thank you David. Absolutely no need to apologize, your support is world-class. You fixed the issue quicker than I was able to reply.

All the best,

Robert