WooCommerce no longer uses the woocommerce_termmeta table, and instead uses the standard WordPress termmeta table. So you shouldn’t actually have this table any longer.
Thanks Thomas, Do you have any idea how to get rid of this error?
Have you run the WooCommerce 2.6 database update? You can make sure everything ran correctly by viewing the db update logs at WooCommerce > System Status > Logs.
If everything looks correct there, then you likely have another plugin trying to use this table. Try disabling plugins until you find the one causing this error.
Hi Caleb,
I see this in logs
11-09-2015 @ 20:01:52 – GeoIP API: fseek failed
11-09-2015 @ 20:01:52 – GeoIP API: Error traversing database – perhaps it is corrupt?
— so on
11-10-2015 @ 15:29:48 – GeoIP API: fseek failed
11-10-2015 @ 15:29:48 – GeoIP API: Error traversing database – perhaps it is corrupt?
this is in database update log
06-17-2016 @ 22:35:56 – Queuing 2.6.0 – wc_update_260_options
06-17-2016 @ 22:35:56 – Queuing 2.6.0 – wc_update_260_termmeta
06-17-2016 @ 22:35:57 – Queuing 2.6.0 – wc_update_260_zones
06-17-2016 @ 22:35:57 – Queuing 2.6.0 – wc_update_260_zone_methods
06-17-2016 @ 22:35:57 – Queuing 2.6.0 – wc_update_260_refunds
06-17-2016 @ 22:35:57 – Queuing 2.6.0 – wc_update_260_db_version
06-17-2016 @ 22:35:58 – Unable to dispatch WooCommerce updater: Operation timed out after 1000 milliseconds with 0 bytes received
06-17-2016 @ 22:36:10 – Running wc_update_260_options callback
06-17-2016 @ 22:36:10 – Finished wc_update_260_options callback
06-17-2016 @ 22:36:10 – Running wc_update_260_termmeta callback
06-17-2016 @ 22:36:10 – Finished wc_update_260_termmeta callback
06-17-2016 @ 22:36:10 – Running wc_update_260_zones callback
06-17-2016 @ 22:36:10 – Finished wc_update_260_zones callback
06-17-2016 @ 22:36:10 – Running wc_update_260_zone_methods callback
06-17-2016 @ 22:36:10 – Finished wc_update_260_zone_methods callback
06-17-2016 @ 22:36:10 – Running wc_update_260_refunds callback
06-17-2016 @ 22:36:10 – Finished wc_update_260_refunds callback
06-17-2016 @ 22:36:10 – Running wc_update_260_db_version callback
06-17-2016 @ 22:36:10 – Finished wc_update_260_db_version callback
06-17-2016 @ 22:36:10 – Data update complete
One of your extensions may be using woocommerce_termmeta. You’d need to find which one and remove it/update it.
For geoIP, if the database is corrupt and you don’t need geolocation, disable it in WC> Settings > Default customer location.
Hi Mike thanks for your ans but No luck, I deactivated all the woocommerce extensions and got the same error.
I don’t see this error or admin section or frontend its showing when I goto /wp-admin/maint/repair.php and Repair Database.
Not seen that before. It must think it’s used, but in reality we dropped that table a while back. Does it cause anything other than a notice?
No I didn’t find any other issue. Its only showing on Repair Database.
I can second this error. I noticed it while using WP Duplicator. Also not solved by deactivating extensions
Cannot say why – if you’re on latest WP all calls to said table are gone as I said :/
Not sure what else to check to be honest. There’s something still trying to use that table it would seem.
If it’s helpful to the topic, I was only able to use WP Duplicator to move my site from local to live once I deactivated Woocommerce. I also tried doing the same with only the extensions deactivated but it only worked once Woocommerce was deactivated.
Guys just did a quick experiment and performed database repair again with woocommerce deactivated /wp-admin/maint/repair.php and got no error.
Here is the screenshot http://prntscr.com/c0ik2d and here is the screenshot of the error when woocommerce is activate http://prntscr.com/c0iknc
