Critical Error Cannot Index

  • Resolved slimesurfer

    (@slimesurfer)


    5 years, 3 months ago

    Hi,

    Getting the following error which is preventing image optimisation when uploading any images to wordpress media. We have installed Yoast Test, reset indexes and also uninstalled and reinstalled plugin. Up to date WP version 5.6.3. Yoast 15.9. PHP 7.4.

    Here’s the PHP error log:

    There has been a critical error on this website.Learn more about debugging in WordPress. There has been a critical error on this website.
    play@webwax1:~/apps/travelplanners/public$ wp yoast index
    PHP 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, boolean given, called in /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 180 and defined in /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:344
    Stack trace:
    #0 /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php(180): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->is_invalid_ancestor(false, 60, Array)
    #1 /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php(112): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->add_ancestors_for_post(60, 139, Array)
    #2 /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-buil in /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 344
    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, boolean given, called in /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 180 and defined in /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:344
    Stack trace:
    #0 /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php(180): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->is_invalid_ancestor(false, 60, Array)
    #1 /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php(112): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->add_ancestors_for_post(60, 139, Array)
    #2 /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-buil in /srv/users/play/apps/travelplanners/public/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 344

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter slimesurfer

    (@slimesurfer)

    5 years, 3 months ago

    We have also tried wp yoast index –reindex using WP CLI

    devnihil

    (@devnihil)

    5 years, 3 months ago

    @slimesurfer We’re sorry that you are experiencing problems that might be caused by our plugin!

    Just 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.`

    devnihil

    (@devnihil)

    5 years, 3 months ago

    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 3 replies - 1 through 3 (of 3 total)

The topic ‘Critical Error Cannot Index’ is closed to new replies.