Error with 1.2.0
-
Hi Danny,
After updating the plugin to version 1.2.0, I see critical errors in the browser console and the dashboard widget doesn’t show data. It was a bit hard to find the exact error, but I just received an email from my own site with this
Foutdetails =========== Een fout van het type E_ERROR werd veroorzaakt op regelnummer 96 van het bestand /.../wp-content/plugins/koko-analytics/src/class-pageview-aggregator.php. Foutmelding: Uncaught TypeError: gmdate(): Argument #2 ($timestamp) must be of type ?int, float given in /.../wp-content/plugins/koko-analytics/src/class-pageview-aggregator.php:96 Stack trace: #0 /.../wp-content/plugins/koko-analytics/src/class-pageview-aggregator.php(96): gmdate() #1 /.../wp-includes/class-wp-hook.php(310): KokoAnalytics\Pageview_Aggregator->finish() #2 /.../wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters() #3 /.../wp-includes/plugin.php(517): WP_Hook->do_action() #4 /.../wp-content/plugins/koko-analytics/src/class-aggregator.php(106): do_action() #5 /.../wp-includes/class-wp-hook.php(310): KokoAnalytics\Aggregator->aggregate() #6 /.../wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters() #7 /.../wp-includes/plugin.php(517): WP_Hook->do_action() #8 /.../wp-content/plugins/koko-analytics/src/class-admin.php(155): do_action() #9 /.../wp-includes/class-wp-hook.php(310): KokoAnalytics\Admin->show_dashboard_page() #10 /.../wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters() #11 /.../wp-includes/plugin.php(517): WP_Hook->do_action() #12 /.../wp-content/plugins/koko-analytics/src/class-admin.php(147): do_action() #13 /.../wp-includes/class-wp-hook.php(310): KokoAnalytics\Admin->show_page() #14 /.../wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters() #15 /.../wp-includes/plugin.php(517): WP_Hook->do_action() #16 /.../wp-admin/admin.php(259): do_action() #17 /.../wp-admin/index.php(10): require_once('...') #18 {main} thrown
I’ll do some more research and will update here, if I find out more.
Thanks,
Jos Klever
Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
- The topic ‘Error with 1.2.0’ is closed to new replies.