Unable to create database tables – after update to v14

Hi @andyuk2005 can you please provide some additional information:
– Any errors from the time of update that are in your PHP error log
– In your database in the wp_options table, there should be an option named yoast_migrations_free. Can you get the value that is stored there?
– If you install https://www.ads-software.com/plugins/yoast-test-helper/ and use the “reset indexables and migrations” button (Tools -> Yoast Test), does that help or does that show the same error?

Hi djennez, thanks for the reply

Sorry, didn’t have an error log set up.

Can’t see an option for yoast_migrations_free under wp_options.

I installed the helper plugin and rest indexable and migrations. Notification is still there.

Is it too late to set up and error log?

You should be able to set up the error log, hit the reset indexables and migrations button again and visit another page. As long as you’re on 14.0 that should trigger the building of the database tables.

You hit that button and the error is still there?

Hi djennex and Joost,

Yes I hit the button, the notification goes away, but once I visit another page it returns. Says “Yoast SEO feature Indexables tables & migrations has been reset.”, but then after visiting another page I get “Yoast SEO was unable to create the database tables required and as such will not function correctly.”

I’ll set up the error log now.

Just to confirm, I checked and again still can’t see any Yoast table in wp_options in the database even after resetting tables.

Hey folks, checked the logs and I currently have this:

Custom Log: WordPress database error Unknown table ‘5e8ccea7f911ca0ca0d2b1d1.wp_yoast_primary_term’ for query DROP TABLE wp_yoast_primary_term made by do_action(‘admin_post_wordpress-seo-feature-reset’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\WP\Test_Helper\WordPress_Plugin_Features->handle_reset_feature, Yoast\WP\Test_Helper\WordPress_Plugin_Features->reset_feature, Yoast\WP\Test_Helper\WordPress_Plugins\Yoast_SEO->reset_feature, Yoast\WP\Test_Helper\WordPress_Plugins\Yoast_SEO->reset_indexables

Is that from when I tried to reset tables though? Shouldn’t there be errors before this?

Hi all,

Thanks for your reports! I’m looking for some specifics on your database connection setups, if you know them. If you’re on the WP slack, please reach out to me there.

Deactivate and remove the Yoast plugin. Download wordpress-seo. 14.0. Go to new plugin, upload the zip file and activate plugin. Done!

@jeanlortye that might fix it for some if the update didn’t work as it should have, which unfortunately sometimes happens with WordPress, I think the larger issue here is particular DB connections that we’re not setting up correctly.

We know the fix.

For the technically savvy: it’s not something we like to do, but we’re going to do it anyway: we had gotten rid of WPDB as we implemented our new ORM and instead opened the database connection directly. Unfortunately this leads to all these problems. So we’re going to make our ORM use the WPDB query functionality and not do that. We have a bit of work to do today and probably tomorrow.

Just updated to 14.0.2 but still got the issue.

I can see from the release notes that it says “For sites with more than 10,000 posts, we advise using the WP CLI command to do the indexation on the server.”

I haven’t got more than 10,000 posts, but either way I don’t know how I should be do indexation.

Would this be done by the Yoast plugin?

I did reset indexables on the Yoast Test plugin, but still no luck.

If Yoast could walk through the process or indexation then that’d be great to get this resolved!

OKay I can see the following on the error log:

WordPress database error Table ‘wp_yoast_indexable’ already exists for query CREATE TABLE wp_yoast_indexable (

Would anyone be able to walk me through how to resolve that? I don’t want to go removing tables and making things worse!

Folks, if you continue to have issues following the latest update, please START YOUR OWN TOPIC. I’m closing this one as it seems to have run its course.