• Resolved martydesign

    (@martydesign)


    I’m getting following error when activated Yoast SEO and trying to save menu, when deactivate, everything works fine.
    Fatal error: Uncaught TypeError: Argument 1 passed to Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder::is_invalid_ancestor() must be an instance of Yoast\WP\SEO\Models\Indexable, bool given, called in /home/zimnucom/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 176 and defined in /home/zimnucom/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:340 Stack trace: #0 /home/zimnucom/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php(176): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->is_invalid_ancestor(false, 659, Array) #1 /home/zimnucom/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php(182): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->add_ancestors_for_post(659, 300, Array) #2 /home/zimnucom/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php(112): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->add_an in /home/zimnucom/public_html/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 340

Viewing 5 replies - 1 through 5 (of 5 total)
  • @martydesign

    We apologize for the difficulties you’re having while installing the plugin.

    Fatal errors are common and they are usually related to the cache. Try clearing the cache from your theme, plugin, server, browser and CDN (e.g. CloudFlare). If you are not sure how to clear the cache from a theme or plugin please speak to those authors.

    Sometimes, deleting the plugin and reinstall would also solves the error.

    If that doesn’t solve, to be sure, we would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?

    Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

    As we can imagine that 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.

    Let us know how that goes.

    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.

    clippingpathspecialists

    (@clippingpathspecialists)

    I am having the similar issue, i can’t edit the webstories of my site.
    Fatal error: Uncaught TypeError: Argument 1 passed to Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder::is_invalid_ancestor() must be an instance of Yoast\WP\SEO\Models\Indexable, bool given, called in /home/customer/www/clippingpathspecialists.com/public_html/wp-content/plugins/yoast-seo-premium/vendor/yoast/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 176 and defined in /home/customer/www/clippingpathspecialists.com/public_html/wp-content/plugins/yoast-seo-premium/vendor/yoast/wordpress-seo/src/builders/indexable-hierarchy-builder.php:340 Stack trace: #0 /home/customer/www/clippingpathspecialists.com/public_html/wp-content/plugins/yoast-seo-premium/vendor/yoast/wordpress-seo/src/builders/indexable-hierarchy-builder.php(176): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->is_invalid_ancestor(false, 433, Array) #1 /home/customer/www/clippingpathspecialists.com/public_html/wp-content/plugins/yoast-seo-premium/vendor/yoast/wordpress-seo/src/builders/indexable-hierarchy-builder.php(112): Yoast\WP\S in /home/customer/www/clippingpathspecialists.com/public_html/wp-content/plugins/yoast-seo-premium/vendor/yoast/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 340

    Redpik

    (@redpik)

    Same bug here.

    Hi,
    Please re-open this ticket. We are having the exact same issue.
    It’s very frustrating for our clients. Our work around involves disabling Yoast, making menu updates, then re-enabling Yoast again.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal error when saving menu’ is closed to new replies.