• Resolved banec

    (@banec)


    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 2 replies - 16 through 17 (of 17 total)
  • Thread Starter banec

    (@banec)

    @turkeysforlife thank you. I rolled back to Yoast 21.7, which at least fixed my issues with WP Recipe Maker, however, I still have the fatal error in py “Posts” menu.

    Plugin Author Enrico Battocchi

    (@lopo)

    @banec sorry to see you’re still experiencing issues.
    If you use the WooCommerce Produce tabs plugin, we would recommend to upgrade to version 2.1.1, it should solve the issue (see here our communication with their dev team).
    If it’s not the case, we’d suggest to try to disable all the other plugins one by one to find which one is causing this incompatibility by not following the WordPress documentation for this WP filter. The part of our plugin triggering the error has not been changed since version 5.6 (2017) so it should be another plugin which has recently changed its code to introduce this problem.
    Please keep us updated if you can, we may assist in contacting the third party plugin’s authors to find a solution.

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘Fatal error: Uncaught TypeError’ is closed to new replies.