Title: Uncaught Error Last modified: September 24, 2021 --- # Uncaught Error * Resolved [mdebruce](https://wordpress.org/support/users/mdebruce/) * (@mdebruce) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/) * Hello, I have the same issue as two people here, down to the same error on the same lines of code as per this reply: [https://wordpress.org/support/topic/is-yoast-incompatible-with-new-wordpress-version/#post-14902950](https://wordpress.org/support/topic/is-yoast-incompatible-with-new-wordpress-version/#post-14902950) * `An error of type E_ERROR was caused in line 129 of the file /wp-content/plugins/ wordpress-seo/src/memoizers/meta-tags-context-memoizer.php. Error message: 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 wp-content/plugins/wordpress-seo/src/integrations/blocks/breadcrumbs-block. php on line 104 and defined in wp-content/plugins/wordpress-seo/src/memoizers/ meta-tags-context-memoizer.php:129 Stack trace: #0 /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 /wp-includes/class-wp- block.php(221): Yoast\WP\SEO\Integrations\Blocks\Breadcrumbs_Block->present(Array,”, Object(WP_Block)) #2 /wp-includes/blocks.php(868): WP_Block->render() #3 //wp- includes/blocks.php(906): render_block(Array) * I got a critical error when I tried to edit the one page I used the Yoast SEO breadcrumb block in, everything else was fine. It was the first time I tried using it. * I was able to use recovery mode to remove the block to be able to exit recovery mode. Everything works again but I have deactivated yoast in the meantime. * WordPress version 5.8.1 Current plugin: Yoast SEO (version 17.2) PHP version 7.3.27 Viewing 9 replies - 1 through 9 (of 9 total) * [Suwash Kunwar](https://wordpress.org/support/users/suascat_wp/) * (@suascat_wp) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14908239) * [@mdebruce](https://wordpress.org/support/users/mdebruce/) * This is most likely a WordPress update quirk. If you remove and reinstall the plugin, you should not have this issue anymore. * Please clear all your caching from your theme, plugin, server, CDN like CloudFlare or browser. If you are not sure how to clear caching from theme/plugin please speak to those authors. If you want to clear cache from the server, please speak to your host provider. To clear the cache from a browser use this guide: [https://kb.yoast.com/kb/how-to-clear-my-browsers-cache/](https://kb.yoast.com/kb/how-to-clear-my-browsers-cache/). * Thread Starter [mdebruce](https://wordpress.org/support/users/mdebruce/) * (@mdebruce) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14908982) * Thank you, I’ve reinstalled now, cleared the cache in my plugin folder, and browser cache. I haven’t tried using the breadcrumb block again, but I’ve got the breadcrumb code back in my site now so thank you. * [Suwash Kunwar](https://wordpress.org/support/users/suascat_wp/) * (@suascat_wp) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14909205) * [@mdebruce](https://wordpress.org/support/users/mdebruce/) Thanks for the update. Just to confirm, do you still see those errors? If not, can we close this thread now? * Thread Starter [mdebruce](https://wordpress.org/support/users/mdebruce/) * (@mdebruce) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14909301) * I managed to test the block and it seems to be okay. So yes, this can be closed, thank you. * Thread Starter [mdebruce](https://wordpress.org/support/users/mdebruce/) * (@mdebruce) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14910413) * Yeah, there are a few of us, but the solution works if you have admin rights to uninstall and reinstall Yoast. I might just add a little more info in case it helps anyone else. I have auto-update set for plugins and WP. I have a cache plugin that let’s me know when there are changes to plugins and so encourage clearing cache where appropriate. I encountered this error only when I used the breadcrumbs block, for the first time. And it almost immediately crashed the editor for that page, but only that page. Then WP sent me an email immediately: * > “Since WordPress 5.2 there is a built-in feature that detects when a plugin > or theme causes a fatal error on your site, and notifies you with this automated > email. > In this case, WordPress caught an error with one of your plugins, Yoast > SEO. First, visit your website () and check for any visible issues. Next, visit > the page where the error was caught (post.php?post=xx&action=edit&message=x) > and check for any visible issues. Please contact your host for assistance with > investigating this issue further. If your site appears broken and you can’t > access your dashboard normally, WordPress now has a special “recovery mode”. > This lets you safely login to your dashboard and investigate further.” * I used the recovery mode link, then grabbed the error code and tried looking up previous support requests here, noticed there was at least one other person with the exact same error with no solution at that stage. But yes, uninstalling and reinstalling, clearing plugin cache did work. It’s the age old solution, but it worked. * Plugin Support [Maybellyne](https://wordpress.org/support/users/maybellyne/) * (@maybellyne) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14912291) * [@musicletter](https://wordpress.org/support/users/musicletter/) * **Thank you for bringing this issue to our attention!** * **We apologize** for the trouble you are currently experiencing with our plugin. You are actually not the first to report this issue. That means a bug report has been created and is under review by our product team. * **What’s next?** Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they’ll start working on your report. * If you have any further information that may affect the prioritization or help our development team solve this bug, please feel invited to reply to this forum topic. * Thread Starter [mdebruce](https://wordpress.org/support/users/mdebruce/) * (@mdebruce) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14918040) * Thank you for sharing that! I’ll do a check of my installation and test it and come back with any results. I quite like the way I have the breadcrumbs coded and will probably stick with it, but I have another site I need to put bread crumbs into and this might still be a block I want to use in the future. And thanks to the team, not sure if they get to see that, so I’ll check the other threads 🙂 * Plugin Support [Michael Tiña](https://wordpress.org/support/users/mikes41720/) * (@mikes41720) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14926952) * Hi [@mdebruce](https://wordpress.org/support/users/mdebruce/) & [@musicletter](https://wordpress.org/support/users/musicletter/) * [Updating to the latest version of Yoast SEO v17.2.1](https://yoast.com/help/how-can-i-update-my-free-plugin/) should fix the fatal error related to the breadcrumb block for auto-draft posts without an indexable. * Please do update to v17.2.1 and see if this resolves the issue regarding the reported fatal error. * Thanks again! * Plugin Support [Michael Tiña](https://wordpress.org/support/users/mikes41720/) * (@mikes41720) * [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14949912) * Hello, * Please do update to the latest version of Yoast SEO (currently v17.3) and we suspect this fatal error should be resolved accordingly. * We’ll be setting this forum thread to closed in order to keep the overview going. Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Uncaught Error’ is closed to new replies. * ![](https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908) * [Yoast SEO - Advanced SEO with real-time guidance and built-in AI](https://wordpress.org/plugins/wordpress-seo/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-seo/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordpress-seo/) * [Active Topics](https://wordpress.org/support/plugin/wordpress-seo/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-seo/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordpress-seo/reviews/) ## Tags * [Yoast](https://wordpress.org/support/topic-tag/yoast/) * 9 replies * 5 participants * Last reply from: [Michael Tiña](https://wordpress.org/support/users/mikes41720/) * Last activity: [4 years, 8 months ago](https://wordpress.org/support/topic/uncaught-error-31/#post-14949912) * Status: resolved