• Resolved tomtc

    (@tomtc)


    After updating to Yoast 16.1 we get error 500 when trying to save Elementor templets. Below is PHP error. When downgrading to Yoast 16.0.2 then the problem is gone.

    
    PHP Fatal error:  Uncaught TypeError: Argument 1 passed to Yoast\\WP\\SEO\\Builders\\Index
    able_Hierarchy_Builder::build() must be an instance of Yoast\\WP\\SEO\\Models\\Indexable, bool given, called in /srv/www/joi.dev01.effipress.com/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php on
     line 175 and defined in /srv/www/joi.dev01.effipress.com/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:102\nStack trace:\n#0 /srv/www/joi.dev01.effipress.com/wp-content/plugins/wordpress-seo/src/integrati
    ons/watchers/indexable-ancestor-watcher.php(175): Yoast\\WP\\SEO\\Builders\\Indexable_Hierarchy_Builder->build(false)\n#1 /srv/www/joi.dev01.effipress.com/wp-includes/class-wp-hook.php(294): Yoast\\WP\\SEO\\Integrations\\Watchers\\Indexa
    ble_Ancestor_Watcher->build_post_hierarchy(217)\n#2 /srv/www/joi.dev01.effipress.com/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters('', Array)\n#3 /srv/www/joi.dev01.effipress.com/wp-includes/plugin.php(484):...', referer: ht
    tp://joi.dev01.effipress.com/wp-admin/post.php?post=217&action=elementor
    
    • This topic was modified 3 years, 7 months ago by Yui. Reason: please use CODE button for code formatting
Viewing 4 replies - 1 through 4 (of 4 total)
  • Getting exactly the same issue:

    We’re using Elementor and this was happening when we were developing new templates in the them builder. Deactivating Yoast take the issue away. Issue was not there prior to updating to 16.1

    Server error log (repeated multiple times):
    
    Stack trace:
    #0 …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php(175): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->build(false)
    #1 …/lcc-site-2021/wp-includes/class-wp-hook.php(294): Yoast\WP\SEO\Integrations\Watchers\Indexable_Ancestor_Watcher->build_post_hierarchy(2353)
    #2 …/lcc-site-2021/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
    #3 … in …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 102
    
    Email message with error info:
    
    

    An error of type E_ERROR was caused in line 102 of the file …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php. Error message: Uncaught TypeError: Argument 1 passed to YoastWPSEOBuildersIndexable_Hierarchy_Builder::build() must be an instance of YoastWPSEOModelsIndexable, bool given, called in …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php on line 175 and defined in …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:102
    Stack trace:
    #0 …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php(175): YoastWPSEOBuildersIndexable_Hierarchy_Builder->build(false)
    #1 …/lcc-site-2021/wp-includes/class-wp-hook.php(294): YoastWPSEOIntegrationsWatchersIndexable_Ancestor_Watcher->build_post_hierarchy(2334)
    #2 …/lcc-site-2021/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
    #3 …

    Any help you and give would be much appreciated.`

    • This reply was modified 3 years, 7 months ago by garyjh28.

    I’m experiencing the same issue:

    Détails de l’erreur
    ======================
    Une erreur de type E_ERROR a été causée dans la ligne 102 du fichier ***/www/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php. Message d’erreur : Uncaught TypeError: Argument 1 passed to Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder::build() must be an instance of Yoast\WP\SEO\Models\Indexable, boolean given, called in ***/www/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php on line 175 and defined in ***/www/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:102
    Stack trace:
    #0 ***/www/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php(175): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->build(false)
    #1 ***/www/wp-includes/class-wp-hook.php(294): Yoast\WP\SEO\Integrations\Watchers\Indexable_Ancestor_Watcher->build_post_hierarchy(6851)
    #2 ***/www/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
    #3 ***/www/wp-includes/plugin.php(484): WP_Hook->do_action(Array)
    #4 ***/www/wp-includes/taxonomy.php(2737): do_action('set_object_term...', 6851, Array, Ar
    • This reply was modified 3 years, 7 months ago by pierreripka.

    Hi @tomtc & @digitay !

    Thank you for reaching out and letting us know. We were able to reproduce this issue on our local test sites when trying to either create a new or update an existing Elementor template. We have created an internal bug report for our development team. Happy to hear that downgrading to 16.0.2 has temporarily resolved the issue for you @tomtc.

    Plugin Support devnihil

    (@devnihil)

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘version 16.1 gives error 500 when saving Elementor templates’ is closed to new replies.