Title: Fatal error: Uncaught TypeError Last modified: January 23, 2024 --- # Fatal error: Uncaught TypeError * Resolved [banec](https://wordpress.org/support/users/banec/) * (@banec) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/) * After updating to 21.8.1 I’m getting a fatal error on my blog posts page. Updating to 21.9 did not solve the issue. After deactivating the plugin the error is gone, so it’s caused by it for sure. Here is the full error: **Fatal error**: Uncaught TypeError: Argument 1 passed to WPSEO_Abstract_Post_Filter::add_filter_link() must be of the type array, null given, called in /home/customer/www/levoit.bg/ public_html/wp-includes/class-wp-hook.php on line 324 and defined in /home/customer/ www/levoit.bg/public_html/wp-content/plugins/wordpress-seo/admin/filters/class- abstract-post-filter.php:103 Stack trace: #0 /home/customer/www/levoit.bg/public_html/ wp-includes/class-wp-hook.php(324): WPSEO_Abstract_Post_Filter->add_filter_link( NULL) #1 /home/customer/www/levoit.bg/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array) #2 /home/customer/www/levoit.bg/public_html/ wp-admin/includes/class-wp-list-table.php(515): apply_filters(‘views_edit-post’, Array) #3 /home/customer/www/levoit.bg/public_html/wp-admin/edit.php(486): WP_List_Table- >views() #4 {main} thrown in **/home/customer/www/levoit.bg/public_html/wp-content/ plugins/wordpress-seo/admin/filters/class-abstract-post-filter.php** on line ** 103** Viewing 15 replies - 1 through 15 (of 17 total) 1 [2](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/page/2/?output_format=md) [→](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/page/2/?output_format=md) * [ericreynolds007](https://wordpress.org/support/users/ericreynolds007/) * (@ericreynolds007) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17365152) * I am receiving the same error. I had to remove the plugin manually via ftp. 🙁 * Thread Starter [banec](https://wordpress.org/support/users/banec/) * (@banec) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17365177) * For me just deactivating it works, however, I prefer to keep using it.. * [Stina](https://wordpress.org/support/users/kristnaus/) * (@kristnaus) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17365227) * I have the same situacion. When active seo plugin, then can’t use edit blog posts. What is the possible solution to the situation? * [doly77](https://wordpress.org/support/users/doly77/) * (@doly77) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17365595) * Same situation on my blog * [jolmedo](https://wordpress.org/support/users/jolmedo/) * (@jolmedo) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17365672) * I have a similar problem with Woocommerce products * Plugin Support [Jose Varghese](https://wordpress.org/support/users/josevarghese/) * (@josevarghese) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17365870) * Hi everyone, * Thanks for using the Yoast SEO plugin and for reporting this to us. Can you please let us know whether you are using the ‘WooCommerce Product Tabs by Barn2 Plugins’ on your website? * If yes, the fatal error you have noticed would be due to the specific plugin, and our development team has already opened an issue on their plugin forum with more details on why the issue occurs and how to fix it at their end; you[ can read more here](https://wordpress.org/support/topic/v2-1-0-fatal-erro-with-yoast/). * In case if you are not using the above mentioned plugin, please let us know. * [imds](https://wordpress.org/support/users/imds/) * (@imds) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17365905) * Hi, * When upgrading to 21.9 we also noticed issues, might be related to this but it does seem to return a different error code. Deactivating the plugin via FTP was our fix as well. We should clarify that we do not use WooCommerce. * Got error ‘PHP message: PHP Fatal error: Uncaught TypeError: ftp_nlist(): Argument# 1 ($ftp) must be of type FTP\\Connection, null given in /var/www/www.xxxxx.xxx/ wp-admin/includes/class-wp-filesystem-ftpext.php:438 - This reply was modified 2 years, 4 months ago by [imds](https://wordpress.org/support/users/imds/). * [turkeysforlife](https://wordpress.org/support/users/turkeysforlife/) * (@turkeysforlife) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17365930) * We also had this problem and rolling back to the previous version of Yoast solved the issue. We also don’t use anything at all relating to WooCommerce. We do, however, use the WP Recipe Maker plugin and, since Yoast updated, they have also updated their plugin with the changelog saying:“Fix: Error caused by Yoast SEO suddenly removing constant”Hopefully that might help troubleshoot? * Plugin Support [Jose Varghese](https://wordpress.org/support/users/josevarghese/) * (@josevarghese) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17365970) * Hi [@imds](https://wordpress.org/support/users/imds/) * Thanks for replying to this. We are sorry you’re having the same issue. Kindly please [open a new request](https://wordpress.org/support/plugin/wordpress-seo#new-post) and share more details about the PHP version you are using and also more details on whether you have performed the conflict check already with the Yoast SEO plugin as activated first or not. That way, it’s easier to track issues and provide assistance. Thanks! * We can imagine that deactivating plugins or switching themes **on your production site** isn’t the best way to go as you notice a fatal error. Do you have or would you be willing to set up a **staging environment** to run additional tests without interfering with your live site? * **No staging environment is available for testing** A staging environment is a copy of your site on your server that allows you to implement and test changes without affecting your live site. Some popular web hosts offer quick setups for a staging site. Please contact your web host to see if this option is available for your site. You can [create a staging site](https://yoast.com/help/how-to-create-a-staging-environment-for-your-wordpress-site/#utm_source=support&utm_medium=email&utm_campaign=support-link&utm_content=link) using a WordPress plugin if your web host does not offer staging environments. * **Are you not aware of how to perform a conflict check**? Don’t worry. Often, we see problems occur in combination with another plugin or theme. The fastest way to rule out any conflict is to **deactivate all non-Yoast plugins and switch to a standard theme** like [Twenty Twenty-Two](https://wordpress.org/themes/twentytwentytwo/). * Please test this on your development or staging site if you have one. If not, we recommend using the [Health Check & Troubleshooting](https://wordpress.org/plugins/health-check/) plugin. * If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: [How to check for plugin conflicts](https://yoast.com/help/how-to-check-for-plugin-conflicts/).** When you activate the troubleshooting mode, kindly make sure that the Yoast SEO plugin is activated first**, then check whether the issue occurs or not. * We hope you will open a new ticket, so it will be helpful for us to narrow down the issue. * Plugin Author [Enrico Battocchi](https://wordpress.org/support/users/lopo/) * (@lopo) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17366114) * Thanks for the heads up [@turkeysforlife](https://wordpress.org/support/users/turkeysforlife/)! But that should not be related (it looks like they used a constant that we deprecated more than one year ago). * [jolmedo](https://wordpress.org/support/users/jolmedo/) * (@jolmedo) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17366284) * Thanks for the quick response, Jose, but I’m afraid not, I’m not using the ‘WooCommerce Product Tabs by Barn2 Plugins’ * Plugin Support [Maybellyne](https://wordpress.org/support/users/maybellyne/) * (@maybellyne) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17367457) * [@jolmedo](https://wordpress.org/support/users/jolmedo/): We are sorry you’re having the same issue. Please [open a new request](https://wordpress.org/support/plugin/wordpress-seo#new-post). That way, it’s easier to track issues and provide assistance. Thanks! * [turkeysforlife](https://wordpress.org/support/users/turkeysforlife/) * (@turkeysforlife) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17368158) * [@lopo](https://wordpress.org/support/users/lopo/) Just a follow up that our host (BigScoots) also now has a warning message in the dashboard: “Do not upgrade Yoast to 21.9 if you also run WP Recipe Maker. Doing so may cause your posts to fail to load their content. If you’ve already upgraded, please reach out to support for assistance with a downgrade.” * Thread Starter [banec](https://wordpress.org/support/users/banec/) * (@banec) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17368183) * I’m running WP Recipe Maker as well… and my posts are not working. How can I downgrade Yoast? * [https://cosori.bg/pork-katsu/](https://cosori.bg/pork-katsu/) * [turkeysforlife](https://wordpress.org/support/users/turkeysforlife/) * (@turkeysforlife) * [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/#post-17368270) * [@banec](https://wordpress.org/support/users/banec/) We use [WP Rollback](https://wordpress.org/plugins/wp-rollback/)– always a good plugin to have in reserve. Viewing 15 replies - 1 through 15 (of 17 total) 1 [2](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/page/2/?output_format=md) [→](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/page/2/?output_format=md) The topic ‘Fatal error: Uncaught TypeError’ 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 * [fatal error](https://wordpress.org/support/topic-tag/fatal-error/) * 17 replies * 10 participants * Last reply from: [Enrico Battocchi](https://wordpress.org/support/users/lopo/) * Last activity: [2 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-uncaught-typeerror-28/page/2/#post-17373998) * Status: resolved