• Resolved markofapproval

    (@markofapproval)


    Hey guys,

    I had an error that was causing the products post type page (on the admin side) to keep hanging. A few clients witnessed it. It only seemed to last for half a day but one website I had to deactivate yoast for 2 days.

    I just reactivated it now to get more error details but it is somehow self resolved.

    I am posting the original error log here for reference. Anybody know what could have gone wrong? Maybe custom taxonomies attached to the products post type? Will this same error happen again if I leave yoast active?

    `WordPress database error Unknown column ‘I.version’ in ‘where clause’ for query \n\t\t\tSELECT COUNT(P.ID)\n\t\t\tFROM wp_posts AS P\n\t\t\tWHERE P.post_type IN (‘post’, ‘page’, ‘attachment’, ‘product’, ‘astra-advanced-hook’, ‘shortcode’)\n\t\t\tAND P.post_status NOT IN (‘auto-draft’)\n\t\t\tAND P.ID not in (\n\t\t\t\tSELECT I.object_id from wp_yoast_indexable as I\n\t\t\t\tWHERE I.object_type = ‘post’\n\t\t\t\tAND I.version = 1 ) made by require_once(‘wp-admin/admin.php’), do_action(‘admin_init’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\\WP\\SEO\\Integrations\\Admin\\Indexing_Notification_Integration->maybe_create_notification, Yoast\\WP\\SEO\\Integrations\\Admin\\Indexing_Notification_Integration->should_show_notification, Yoast\\WP\\SEO\\Helpers\\Indexing_Helper->get_filtered_unindexed_count, Yoast\\WP\\SEO\\Helpers\\Indexing_Helper->get_unindexed_count, Yoast\\WP\\SEO\\Actions\\Indexing\\Abstract_Indexing_Action->get_total_unindexedPHP message: WordPress database error Unknown column ‘I.version’ in ‘on clause’ for query \n\t\t\tSELECT COUNT(term_id)\n\t\t\tFROM wp_term_taxonomy AS T\n\t\t\tLEFT JOIN wp_yoast_indexable AS I\n\t\t\t\tON T.term_id = I.object_id\n\t\t\t\tAND I.object_type = ‘term’\n\t\t\t\tAND I.version = 1\n\t\t\tWHERE I.object_id IS NULL\n\t\t\t\tAND taxonomy IN (‘category’, ‘post_tag’, ‘post_format’, ‘product_cat’, ‘product_tag’, ‘product_shipping_class’, ‘moa_brand’, ‘moa_cluster’, ‘moa_supplier’) made by require_once(‘wp-admin/admin.php’), do_action(‘admin_init’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\\WP\\SEO\\Integrations\\Admin\\Indexing_Notification_Integration->maybe_create_notification, Yoast\\WP\\SEO\\Integrations\\Admin\\Indexing_Notification_Integration->should_show_notification, Yoast\\WP\\SEO\\Helpers\\Indexing_Helper->get_filtered_unindexed_count, Yoast\\WP\\SEO\\Helpers\\Indexing_Helper->get_unindexed_count, Yoast\\WP\\SEO\\Actions\\Indexing\\Abstract_Indexing_Action->get_total_unindexed’,

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

    (@maybellyne)

    Hello Markofapproval

    We are sorry about the error you experienced while you had Yoast SEO active. This can be annoying but we encourage you to keep the plugin active so as to monitor the error.

    If it happens again, please try resetting the indexables in the database tables by following 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 each reset was successful. Note: this won’t actually erase your SEO data, which is also stored in WordPress’ default tables. It’ll just reset our index (custom tables) for that data.
    4. Go to SEO > Tools, and under SEO data, click the “Start SEO data optimization” button to allow Yoast to rescan your content.

    Could you then check if you aren’t experiencing these errors anymore?

    Thread Starter markofapproval

    (@markofapproval)

    OH thank you that is a very useful tip. I haven’t experienced since 2 days ago even with the plugin active. I will continue to monitor.

    It’s too good a plugin not to leave active 😉
    Much appreciated!

    @markofapproval Thanks for your reply and you’re very welcome. If you should need any further assistance in this matter, please do not hesitate to let us know.

    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 ‘Critical Error that somehow resolved itself’ is closed to new replies.