jdevreede

I only have my live production site, so I cannot extensively test these things. What I did notice is that there is a list given by the AMP plugin mentioning the plugins with AMP incompatibility:

– Wordfence Security
– AdSense Integration WP QUADS
– Imagify
– linkPizza-Manager
– WebP Express
– Contact Form 7
– Cookie Notice & Compliance for GDPR / CCPA

When I deactivate one of these plugins, it disappears from that list.

Here’s the list:

AdSense Integration WP QUADS
Akismet Anti-Spam
AMP
Broken Link Checker
Cloudflare
Contact Form 7
Cookie Notice & Compliance for GDPR / CCPA
Imagify
linkPizza-Manager
Public Post Preview
Public Post Preview Configurator
Redirection
Site Kit by Google
Veen Theme Functions
WebP Express
Wordfence Security
WP Rocket
Yoast SEO

That is strange, for me it still works. But here is a new link to the same image:

https://www.eetman.nl/wp-content/uploads/2022/06/iScreen-Shoter-2022-05-30-174139.420-1.jpg

However please not that there is not much to see, except that:
– I am using the “AMP” plugin.
– It shows a message that i have four “Plugins with AMP incompatibility”
– And a message “Raw validation data which you may want to share with the author so they can fix AMP compatibility”
– That raw data is the .json file in my first post

Thanks for the tip. Here’s the link https://ibb.co/y4D6xym

I don’t see how I can paste or attach an image here in the forum. If you give me your email I’ll send it to you.

Can you tell me why you don’t recommend it?

I finally was able to test the new version. It solved the problem!

Thank you for the speedy response

@suascat_wp

Thanks for your help. I do not have a testing site, so I used the Health Check plugin you recommended.

– it’s health check only mentioned a recommendation for AMP

Then I tested editing a blogpost, these were te results

– with all plugins switched off >>> there were no problems with the autosave
– then with my Veen theme plugins switched on >>> no problems with the autosave
– then with the Veen theme plugins AND Yoast switched on >>> the crash occured
– switching Yoast of again solved it.

So yes, it does seem some sort of conflict between the theme and Yoast

After clearing the caches from cloudflare, autoptimize, the browser and reinstalling Yoast, the error again happend while editing this page

ERROR:

WordPress versie 5.8.1
Huidig thema: Veen Child (versie )
Huidige plugin: Yoast SEO (versie 17.2)
PHP versie 7.4.14

Foutdetails
===========
Een fout van het type E_ERROR werd veroorzaakt op regelnummer 129 van het bestand /home/eetman1q/public_html/wp-content/plugins/wordpress-seo/src/memoizers/meta-tags-context-memoizer.php. Foutmelding: Uncaught TypeError: Argument 1 passed to Yoast\WP\SEO\Memoizers\Meta_Tags_Context_Memoizer::get() must be an instance of Yoast\WP\SEO\Models\Indexable, bool given, called in /home/eetman1q/public_html/wp-content/plugins/wordpress-seo/src/integrations/blocks/breadcrumbs-block.php on line 104 and defined in /home/eetman1q/public_html/wp-content/plugins/wordpress-seo/src/memoizers/meta-tags-context-memoizer.php:129
Stack trace:
#0 /home/eetman1q/public_html/wp-content/plugins/wordpress-seo/src/integrations/blocks/breadcrumbs-block.php(104): Yoast\WP\SEO\Memoizers\Meta_Tags_Context_Memoizer->get(false, 'Post_Type')
#1 /home/eetman1q/public_html/wp-includes/class-wp-block.php(221): Yoast\WP\SEO\Integrations\Blocks\Breadcrumbs_Block->present(Array, '', Object(WP_Block))
#2 /home/eetman1q/public_html/wp-includes/blocks.php(868): WP_Block->render()
#3 /home/eetman1q/public_html/wp-includes/blocks.php(906): render_block(Array)
#4 /home/eetman1q/public_html/wp-includes/class-wp-hook.php(303): do_blocks('

Thanks, I just followed your advice and will monitor if it solved the issue. I’ll let you know if it helped.

Okay, made a new ticket https://www.ads-software.com/support/topic/yoast-seems-to-crash-the-autosave/#new-post

The problem starts as soon as WordPress wants to save a new blogpost.

same here, I’m getting these emails from WordPress:

Sinds WordPress 5.2 is er een ingebouwde functie die herkent wanneer een plugin of thema een fatale fout veroorzaakt op je site en die je op de hoogte stelt met deze automatische e-mail. In dit geval heeft WordPress een probleem gevonden met één van je plugins: Yoast SEO.

WordPress versie 5.8.1
Huidig thema: Veen Child (versie )
Huidige plugin: Yoast SEO (versie 17.2)
PHP versie 7.4.14

Foutdetails
===========
Een fout van het type E_ERROR werd veroorzaakt op regelnummer 129 van het bestand /home/eetman1q/public_html/wp-content/plugins/wordpress-seo/src/memoizers/meta-tags-context-memoizer.php. Foutmelding: Uncaught TypeError: Argument 1 passed to Yoast\WP\SEO\Memoizers\Meta_Tags_Context_Memoizer::get() must be an instance of Yoast\WP\SEO\Models\Indexable, bool given, called in /home/eetman1q/public_html/wp-content/plugins/wordpress-seo/src/integrations/blocks/breadcrumbs-block.php on line 104 and defined in /home/eetman1q/public_html/wp-content/plugins/wordpress-seo/src/memoizers/meta-tags-context-memoizer.php:129
Stack trace:
#0 /home/eetman1q/public_html/wp-content/plugins/wordpress-seo/src/integrations/blocks/breadcrumbs-block.php(104): Yoast\WP\SEO\Memoizers\Meta_Tags_Context_Memoizer->get(false, 'Post_Type')
#1 /home/eetman1q/public_html/wp-includes/class-wp-block.php(221): Yoast\WP\SEO\Integrations\Blocks\Breadcrumbs_Block->present(Array, '', Object(WP_Block))
#2 /home/eetman1q/public_html/wp-includes/blocks.php(868): WP_Block->render()
#3 /home/eetman1q/public_html/wp-includes/blocks.php(906): render_block(Array)
#4 /home/eetman1q/public_html/wp-includes/class-wp-hook.php(303): do_blocks('

Thank you for checking it. I will look into the other resource you refer to.

There are 2 pictures in this article clearly named like the article topic like “Orzo-salade-met-feta-recept-1-950×500.jpeg”.

Both are > the required minimum width:
1st = 950×500 pixels
2nd = 768×768 pixels

So far that still leaves me clueless. Where can I find the sitemap, as there seem to be some requirements as to how these images are in there?