Critical error Unknown column ‘inclusive_language_score’

  • Resolved Nick Verwymeren

    (@greatwitenorth)


    1 year, 7 months ago

    When saving a draft on my website I’m getting a critical error. When I search the logs this is the error that was produced:

    [Thu Aug 17 12:44:43.664432 2023] [proxy_fcgi:error] [pid 26935:tid 139882630301440] [client 67.81.202.202:0] AH01071: Got error ‘PHP message: WordPress database error Unknown column ‘inclusive_language_score’ in ‘field list’ for query INSERT INTO wp_yoast_indexable (object_type, object_id, object_sub_type, permalink, primary_focus_keyword_score, readability_score, inclusive_language_score, is_cornerstone, is_robots_noindex, is_robots_nofollow, is_robots_noimageindex, is_robots_noarchive, is_robots_nosnippet, open_graph_image, open_graph_image_id, open_graph_image_source, open_graph_image_meta, twitter_image, twitter_image_id, twitter_image_source, primary_focus_keyword, canonical, title, description, breadcrumb_title, open_graph_title, open_graph_description, twitter_title, twitter_description, estimated_reading_time_minutes, author_id, post_parent, number_of_pages, post_status, is_protected, is_public, has_public_posts, blog_id, schema_page_type, schema_article_type, object_last_modified, object_published_at, version, permalink_hash, …’,

    I’m using Yoast SEO version 20.13 on WordPress 6.3

    Also, I have the Inclusive Language Analysis set to Off.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Nick Verwymeren

    (@greatwitenorth)

    It looks like the migration for yoast failed (but there was no notificatio that it failed). When I tried to run the migration manually I got:

    ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

    The recommended solution for me was to run the following:

    ALTER TABLE wp_yoast_indexable ROW_FORMAT=DYNAMIC;

    After doing this, I could run the migration.

    Hi @greatwitenorth,

    Thank you so much for reaching out.

    Hmm, odd. It’s not an error I can replicate on a new local site with Yoast SEO 20.13. Have you used the inclusive language feature before and set it to off recently? I tested enabling and disabling it again, but I was able to save drafts of posts and pages just fine.

    What I would recommend is trying to rebuild the indexables tables with our test helper plugin. You can find the steps here: https://yoast.com/help/how-to-reset-yoast-indexables/

    Can you let us know if you can save your drafts after doing so?

    Thread Starter Nick Verwymeren

    (@greatwitenorth)

    @jeroenrotty It seems to be a problem when the database engine for the table is InnoDB. The migration fails with the error I mentioned above.

    Plugin Support Maybellyne

    (@maybellyne)

    Hello Nick,

    Can you let us know if the error continues after trying these steps?

    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 SEO > Tools, and under SEO data, click the “Start SEO data optimization” button to allow Yoast to rescan your content.

    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 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Critical error Unknown column ‘inclusive_language_score’’ is closed to new replies.

Tags