Hi @axibert,
I’m sorry to hear that! Do you have access to the actual error message?
PHP 7.4 is still supported and we’re actively testing for syntax errors on it, so that should not be the issue here. But with the error message, we’ll know right away what is causing it.
Let me know – I’d love to provide a quick fix.
No, I don’t have access to it. What can be done?
If your site is currently not doing anything because of the error, you can deactivate Koko Analytics by removing the /wp-content/plugins/koko-analytics/ directory.
You can then re-install version 1.8.6 from the following ZIP package: https://downloads.wordpress.org/plugin/koko-analytics.1.8.6.zip
If you somehow have access to your PHP error log then that would be really helpful for us in determining the error message so that we can fix it properly.
ok weird, I have reactivated the 2.00 version of the plugin and now it is fine. Not sure what happened there but it is working again after a server restart
-
This reply was modified 4 months ago by
axibert.
That’s weird indeed @axibert – but happy to hear it’s all buzzing along now anyway. Let me know in case you happen to find the error message later on or the issue re-appears.
My entire powerful, dedicated web server and database crashed after updating to 2.0. My host said the database had too many requests and everything had to be reset. I now have the old version back, but we can no longer display all the data. I can no longer see the pages that were accessed, only the referrers.
On another installation, the entire server did not crash. However, there were massive performance issues. Here, too, I reinstalled and activated the old version and reset the data. Since then, no new data has been collected.
-
This reply was modified 4 months ago by
René. Reason: expanded
I also encountered issues after upgrading to version 2.0.0.
After the upgrade, WordPress became unresponsive.
For now, I’ve disabled Koko Analytics.
Here is the error message:
Fatal error: Uncaught Error: Failed opening required '/XXX/public_html/wp-content/plugins/koko-analytics/src/class-aggregator.php' (include_path='.:/opt/php-8.1.32-2/data/pear') in /XXX/public_html/wp-content/plugins/koko-analytics/autoload.php:43 Stack trace: #0 /XXX/public_html/wp-includes/class-wp-hook.php(322): {closure}('KokoAnalytics\A…') #1 /XXX/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array) #2 /XXX/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /XXX/public_html/wp-content/plugins/koko-analytics/koko-analytics.php(131): do_action('koko_analytics_…') #4 /XXX/public_html/wp-includes/class-wp-hook.php(326): KokoAnalytics{closure}(Object(Plugin_Upgrader)) #5 /XXX/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #6 /XXX/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /XXX/public_html/wp-admin/includes/class-plugin-upgrader.php(419): do_action('upgrader_proces…', Object(Plugin_Upgrader), Array) #8 /XXX/public_html/wp-admin/update.php(51): Plugin_Upgrader->bulk_upgrade(Array) #9 {main} Next TypeError: call_user_func(): Argument #1 ($callback) must be a valid callback, class "KokoAnalytics\Aggregator" not found in /XXX/public_html/wp-includes/class-wp-hook.php:322 Stack trace: #0 /XXX/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array) #1 /XXX/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #2 /XXX/public_html/wp-content/plugins/koko-analytics/koko-analytics.php(131): do_action('koko_analytics_…') #3 /XXX/public_html/wp-includes/class-wp-hook.php(326): KokoAnalytics{closure}(Object(Plugin_Upgrader)) #4 /XXX/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #5 /XXX/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #6 /XXX/public_html/wp-admin/includes/class-plugin-upgrader.php(419): do_action('upgrader_proces…', Object(Plugin_Upgrader), Array) #7 /XXX/public_html/wp-admin/update.php(51): Plugin_Upgrader->bulk_upgrade(Array) #8 {main} thrown in /XXX/public_html/wp-includes/class-wp-hook.php on line 322
Environment:
- WordPress: 6.8.2
- PHP: 8.1.32
Stopp your update. I just let my blog at borncity.com/win/ update to version 2.0.1. It failed with only reporting a “critical error” within the WP plugin dashboard. I was notified, that an email shall explain mor. Never received that email.
After that all my six blogs (for instance borncity.com/blog/ borncity.com/senioren/ etc.) stalled -although they are independent WordPress instances with separate data bases.
I used putty to delete the koko analytics plugin folder. But that didn’t help. I was forced to call the support of my provider. The supporter told me, that many database requests blocks the whole hosting package. He startete the php part, so all scripts are reset – afterward my blogs are reachable again. I will deactivate koko analytics now. There is something strange within the plugin update to v 2.x.
PS: I tried to gain a php report. There is only a php-slow report, that didn’t help.
-
This reply was modified 4 months ago by
guenni. Reason: typo
-
This reply was modified 4 months ago by guenni.
Hi @mobiflip,
The plugin has to do a one-time data migration to allow for storing URL path’s, which can take quite some time if you have a website with many different posts or pages.
It sounds like the migration to the new storage has completed partially for you…
At this point you have two options:
- Re-install the files from version 2.0.1 and allow the plugin some time to complete the data migration. This can take several page-loads.
- Stay with version 1.8.6. The plugin should have created a back-up of the affected database table called wp_koko_analytics_post_stats_backup. If you rename this table to wp_koko_analytics_post_stats then you should see your original statistics again.
The backup file has 789,998 records. I’ll see what I can do. In any case, the update killed the entire server and database. @dvankooten
Thanks @mobiflip – I’m reconsidering the migrate-on-the-go approach for such large sites as yours as we speak and looking for alternatives.
I renamed it, but all data for the individual pages remains empty.
I now have the following tables:
wp_koko_analytics_dates
wp_koko_analytics_paths
wp_koko_analytics_post_stats
wp_koko_analytics_referrer_stats
wp_koko_analytics_referrer_urls
wp_koko_analytics_site_stats
The plugin shows a database size of 35 MB. Previously, I believe it was 56 MB. I primarily use koko because of its data protection friendliness, and because it has performed excellently with such large amounts of data so far, there is no point in cluttering up or overloading the database.
The problem is that it seems that no new data is being collected in this area anymore. I can’t see which pages have been accessed.
-
This reply was modified 4 months ago by René.
-
This reply was modified 4 months ago by René. Reason: explained in detail
Thanks for explanation what’s happens during migration. Well, here is the same as for Rene – I have several blogs with huge databases (20,000 posts). The migration of a blog seems to be pushing the hosting package’s utilization beyond its capacity limits, causing everything to come to a standstill. Because it’s still a shared web hosting package, it’s critical.
-
This reply was modified 4 months ago by guenni.
@guenni
Thank you. And I’m terribly sorry for the hiccup.
I have just pushed another attempt at getting 2.x out the door, but this time delaying the migration until a site administrator explicitly clicks a button and without automatically making a back-up of the affected database table.
I’d love to hear how that version works for you.
—
@mobiflip Do you have an earlier database back-up from which you can restore the Koko Analytics database tables for version 1.8.6? If the plugin failed while it was still backing up your existing tables, the back-up table won’t be complete and is therefore not that usable… Sorry.
I have a backup that is several days old. I am now considering starting from scratch and then going directly to 2.x. What is the best way to proceed? @dvankooten
