13.5 -> 14.1 Table ‘wp_yoast_indexable’ already exists

  • Resolved ghassenpflug

    (@ghassenpflug)


    4 years, 6 months ago

    Hi,
    WP 5.4.1, Yoast 13.5, upgrading to 14.1
    We already went through this with 13.5 -> 14.0.x with a git support ticket.
    The uptake was that database needed INDEX support, but that this is insufficient and wp_yoast_indexable must be reset using the Yoast Test Helper plugin.
    So I had been able to upgrade 13.5 -> 14.0.4 on staging site with this workaround.

    Today I upgrades 14.0.4 -> 14.1 on stating site, no problem.
    So I decided finally is the time to upgrade 13.5 on production site.
    13.5 -> 14.1 succeeds, apparently, but then on going to Dashboard the error message appears, which the new debugger can kindly display.
    The issue is that the wp_yoast_indexable table already exists, and this still crashes the upgrade.

    WpYoastIndexable – Error executing ‘query’ with: CREATE TABLE wp_yoast_indexable ( id int(11) UNSIGNED auto_increment NOT NULL, permalink mediumtext, permalink_hash varchar(191), object_id int(11) UNSIGNED, object_type varchar(32) NOT NULL, object_sub_type varchar(32), author_id int(11) UNSIGNED, post_parent int(11) UNSIGNED, title varchar(191), description text, breadcrumb_title varchar(191), post_status varchar(191), is_public tinyint(1), is_protected tinyint(1) DEFAULT ‘0’, has_public_posts tinyint(1), number_of_pages int(11) UNSIGNED, canonical mediumtext, primary_focus_keyword varchar(191), primary_focus_keyword_score int(3), readability_score int(3), is_cornerstone tinyint(1) DEFAULT ‘0’, is_robots_noindex tinyint(1) DEFAULT ‘0’, is_robots_nofollow tinyint(1) DEFAULT ‘0’, is_robots_noarchive tinyint(1) DEFAULT ‘0’, is_robots_noimageindex tinyint(1) DEFAULT ‘0’, is_robots_nosnippet tinyint(1) DEFAULT ‘0’, twitter_title varchar(191), twitter_image mediumtext, twitter_description mediumtext, twitter_image_id varchar(191), twitter_image_source varchar(191), open_graph_title varchar(191), open_graph_description mediumtext, open_graph_image mediumtext, open_graph_image_id varchar(191), open_graph_image_source varchar(191), open_graph_image_meta text, link_count int(11), incoming_link_count int(11), prominent_words_version int(11) UNSIGNED, PRIMARY KEY (id)) DEFAULT CHARSET=utf8; Reason: Table ‘wp_yoast_indexable’ already exists

    Executing “Reset indexables tables & migrations” in the Yoast Test Helper then permits the upgrade to complete.
    I expect this would have been in your fixes fro 14.1, reading the improvements blog post, but it seems this fix did not in fact make it into 14.1

    So the workaround using Yoast Test Helper is still required.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support marcanor

    (@marcanor)

    Hi @ghassenpflug ,

    Thanks for your report. We apologize for the inconvenience.

    It seems that the database tables were created previously on your production site, and upgrading from 13.5 to 14.1 generated this error. However, we are glad to hear you were able to resolve it by resetting the tables.

    We’re working hard on resolving any issues that come up and we expect that this will be the last time that you need to use the Yoast Test Helper.

    Plugin Support Jerlyn

    (@jerparx)

    Hi @ghassenpflug ,

    We’re closing this thread because we haven’t heard back from you in a while. Should you have further questions, please open a new thread.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘13.5 -> 14.1 Table ‘wp_yoast_indexable’ already exists’ is closed to new replies.