Migration 1.9.991 finishes with errors: unknown column post_id

[jmslbam]

Just a FYI:

include('/plugins/koko-analytics/migrations/1.9.991-prepare-post-stats-table.php')
[06-Jan-2026 10:23:15 UTC] WordPress database error Unknown column 'post_id' in 'SELECT' for query SELECT COUNT(DISTINCT(post_id)) FROM wp_koko_analytics_post_stats WHERE post_id IS NOT NULL AND path_id IS NULL made by require('wp-blog-header.php'), require_once('wp-load.php'), require_once('/www/xyz/public/web/wp-config.php'), require_once('wp-settings.php'), do_action('wp_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, KokoAnalytics\{closure}, KokoAnalytics\Migrations->maybe_run, KokoAnalytics\Migrations->run, KokoAnalytics\Migrations->handle_file, include('/plugins/koko-analytics/migrations/1.9.991-prepare-post-stats-table.php')

So I deployed an project via composer and it threw this "error".
So I disabled and enabled the koko plugin to trigger the migration check, which solved it.

Xoxo

[dannyvankooten]

Interesting @jmslbam - do you happen to recall what version of Koko Analytics you were coming from before this error occurred?

[jmslbam]

1.3.13 😁

[dannyvankooten]

It's really weird because in that migration file, there are these 3 lines:

// prepare columns
$wpdb->query("ALTER TABLE {$wpdb->prefix}koko_analytics_post_stats CHANGE COLUMN id post_id INT UNSIGNED");
$wpdb->query("ALTER TABLE {$wpdb->prefix}koko_analytics_post_stats ADD COLUMN path_id INT UNSIGNED");

$results = $wpdb->get_var("SELECT COUNT(DISTINCT(post_id)) FROM {$wpdb->prefix}koko_analytics_post_stats WHERE post_id IS NOT NULL AND path_id IS NULL");

First query renames the column, third query is throwing the error saying "unknown column post_id"...

Does this particular site have post ID values larger than 4294967295? Only thing I can think of right now...

[jmslbam]

Hier, weer. Maar nu bij een ander project waar ik een db dump van productie naar lokaal haal en waar op productie Koko voorliep en lokaal er dus nog geen migratie is geweest.

Ik werk in wp-admin en hij blijft hangen, waar kan ik een koko.sql db dump naar toe sturen, ik heb het het project een beetje opgeschoond, maar genoeg zodat er nog gedebugged kan worden.

Ik loop ik hier even over, dus kan niet uitgebreid meezoeken met je.

xoxo

[jmslbam]

WordPress database error: [Unknown column 'post_id' in 'field list']
SELECT COUNT(DISTINCT(post_id)) FROM wp_koko_analytics_post_stats WHERE post_id IS NOT NULL AND path_id IS NULL

[jmslbam]

Ik bedenk mij nu net, dat het mss is dat in de DB mss een versie opgeslagen is, maar de tabel zelf nog niet aangepast is.
Doe je zoiets? Anders slaan bijv. de versie op of dat een migratie wel of niet gedraaid heeft.

[dannyvankooten]

@jmslbam Indeed! The plugin checks the koko_analytics_version option (wp_options) and runs any migration files from that value until the current version (based on the KOKO_ANALYTICS_VERSION PHP constant).

Are you dumping all database tables from production or only a subset, ie maybe excluding the options table?

[jmslbam]

Dumping all the tables from production.

I know it's the most sane and most effective way to do migrations like you did, because Gravity Froms checks table structure on every request and that's one of the slower queries in the stack.

Know that I think about it, maybe a button in the back-end like Woo/Gravity Forms that trigger the migrations again instead of trying to solve this/my weird workflow. Because you're not doing anything wrong ;)

[dannyvankooten]

Dumping all the tables from production.

I don't really understand why it even decided to run migrations, because if you're pulling in all tables from production then that should also be pulling in the koko_analytics_version option, right?

Know that I think about it, maybe a button in the back-end like Woo/Gravity Forms that trigger the migrations again instead of trying to solve this/my weird workflow. Because you're not doing anything wrong ;)

I like that, but I would also really like to fix this properly though. Please know that you can already trigger all migrations from a given version by going to ?koko_analytics_migrate_from_version=1.3.13 while logged in as an administrator.

Is there anything specific about this set-up in terms of the database, ie using transactions or anything of that sort?

[dannyvankooten]

Ik werk in wp-admin en hij blijft hangen, waar kan ik een koko.sql db dump naar toe sturen, ik heb het het project een beetje opgeschoond, maar genoeg zodat er nog gedebugged kan worden.

support@kokoanalytics.com (komt bij mij), heel fijn!