• Resolved pandowata

    (@pandowata)


    Hi,
    after updating to 19.11 version we get a fatal error on post created in custome post type

    Error below
    Fatal error: Uncaught TypeError: Argument 1 passed to Yoast\WP\SEO\Generators\Breadcrumbs_Generator::Yoast\WP\SEO\Generators\{closure}() must be an instance of Yoast\WP\SEO\Models\Indexable, bool given in /home/domains/example.com/public_html/wp-content/plugins/wordpress-seo/src/generators/breadcrumbs-generator.php:141 Stack trace: #0 [internal function]: Yoast\WP\SEO\Generators\Breadcrumbs_Generator->Yoast\WP\SEO\Generators\{closure}() #1 /home/domains/example.com/public_html/wp-content/plugins/wordpress-seo/src/generators/breadcrumbs-generator.php(168): array_map() #2 /home/domains/example.com/public_html/wp-content/plugins/wordpress-seo/src/presentations/indexable-presentation.php(765): Yoast\WP\SEO\Generators\Breadcrumbs_Generator->generate() #3 /home/domains/example.com/public_html/wp-content/plugins/wordpress-seo/src/presentations/abstract-presentation.php(64): Yoast\WP\SEO\Presentations\Indexable_Presentation->generate_breadcrumbs() #4 /home/d in /home/domains/example.com/public_html/wp-content/plugins/wordpress-seo/src/generators/breadcrumbs-generator.php on line 141

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Maybellyne

    (@maybellyne)

    Hello @pandowata,

    I’m sorry about the fatal error. First, please set WP_DEBUG and WP_DEBUG_LOG to true, so the error isn’t visible to site visitors:

    // Enable WP_DEBUG mode
    define( 'WP_DEBUG', true );
    
    // Enable Debug logging to the /wp-content/debug.log file
    define( 'WP_DEBUG_LOG', true );

    Next, what PHP version are you using? A Site Health site info copy would be good for us to understand your site better. You can find this under WordPress > Tools > Site Health > Info (tab) > Copy site info button.

    Finally, are you using the wpseo_breadcrumb_links or wpseo_breadcrumb_single_link_info filters to customize your breadcrumbs output?

    We look forward to hearing from you.

    Hey, I have the same problem,
    When I replace :
    $callback = function ( Indexable $ancestor ) {
    with
    $callback = function ( ) {

    The site works… Is there a fix for this?
    Thanks
    Christophe

    Hello, just empty the “yoast_indexable” table and the problem will be solved ??

    Same error can confirm emptying “yoast_indexable” table works.

    Plugin Support devnihil

    (@devnihil)

    @cyber69 @fhqmd Thanks for posting your solution.

    @pandowata Can you please try resetting the indexables data? We have a guide that walks you through how to do this available here: ?How to reset the Yoast indexables. We’ve also summarized the steps below.

      1. Install & activate the?Yoast Test Helper plugin
      2. Go to Tools > Yoast Test
      3. Locate the Yoast SEO section and click on the ‘Reset indexables tables & migrations’, ‘Reset Prominent words calculation’, and ‘Reset Internal link counter’ buttons. After each click, the page will reload to confirm that the specific reset was successful.
      4. Go to Yoast SEO > Tools, and under Optimize SEO Data, click the “Start SEO data optimization” button to allow Yoast to rescan your content.

    Please let us know if the reported issue remains after resetting the optimized data.

    This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic. Please read this post before opening a new request.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘fatal error on pages of custom post type after update to v.19.11’ is closed to new replies.