PHP Fatal error after updating Piwik to 2.14.0

This is a known Piwik issue, see https://github.com/piwik/piwik/issues/8311

Please update to Piwik 2.14.1 as soon as it is available. Meanwhile, you can use WP-Piwik in “Self-hosted (HTTP API)” mode.

If only the configuration interface was available. ??
Changing it in the database would work of course (I switched to manual tracking code for now).

Good point ??

UPDATE wp_options SET option_value = 'http' WHERE option_name = 'wp-piwik_global-piwik_mode';
UPDATE wp_options SET option_value = 'https://FULL_PIWIK_URL/' WHERE option_name = 'wp-piwik_global-piwik_url';

This should work (change to UPDATE wp_sitemeta SET meta_value = [...] WHERE meta_key = [...] on multisites).

There seems to be a workaround for the PHP API: https://forum.piwik.org/read.php?2,127892,page=1#msg-127962

Since the 2.14.1 milestone still has around 30 open issues it might be worth a shot for people that do not want to use the http api until the next Piwik release arrives.

Thank you. I will provide an update this evening.

Unfortunately, this broke my WP-Admin dashboard too. The fix on Piwik’s forum referenced above didn’t fix it for me. I’m a bit confused about this:

UPDATE wp_options SET option_value = 'http' WHERE option_name = 'wp-piwik_global-piwik_mode';
UPDATE wp_options SET option_value = 'https://FULL_PIWIK_URL/' WHERE option_name = 'wp-piwik_global-piwik_url';

Are those SQL commands?

Regards,
Kory

EDIT: Unfortunately, this didn’t work for me. Dashboard is still broken. Also, it doesn’t look like Piwik released 2.14.1 yet so not sure where to get that. I’ll probably have to restore from backup although I did a lot of work today. Gotta love it.

Yes, these are SQL commands to switch to HTTP mode instead of PHP mode. (Please note you have to modify these commands related to your configuration.) The HTTP mode still works, the bug affects the PHP mode only.

Otherwise, we currently just can wait for Piwik 2.14.1. I also tested the workaround, but it did not fix the problem.

Thx, Braekling. I worked with the SQL query above and changed the syntax to my config but still no go. I temporarily disabled the plugin by changing the plugin directory name and my dashboard came right up. That being said, I’ll just wait for 2.14.1 and revert the plugin directory name back after I confirm the issue’s been resolved on the Piwik again.

Have a good weekend.

Regards,
Kory

The following worked for me.. now the WP-Piwik plugin is working again in HTTP mode.

UPDATE wp_options SET option_value = ‘http’ WHERE option_name = ‘wp-piwik_global-piwik_mode’;

If you aren’t familiar with working in command line SQL, you can always use phpMyAdmin (if installed on your server) to access the “wp_options” table and set the “wp-piwik_global-piwik-mode” row back to a value of “http”

Thanks for the help braekling!

Wow, that was one horrible update. Actually two horrible updates: both 2.14.0 and 2.14.1 break the wp-piwik plugin.

I’ve ended up reverting to 2.13.1, and things work again.

We are still working on this.

https://github.com/piwik/piwik/issues/8311
https://github.com/piwik/piwik/issues/8365

2.14.2 is already announced and hopefully will contain a fix. This is all I can do at the moment. ??

2.14.2 milestone: https://github.com/piwik/piwik/milestones/2.14.2

Again: If you updated to Piwik 2.14.0/1 already and you are not able to downgrade to Piwik 2.13.x, you can get WP-Piwik working again by switching to PHP mode. Because the options page is not available anymore, you have to change this in your database.

UPDATE wp_options SET option_value = 'http' WHERE option_name = 'wp-piwik_global-piwik_mode';

If you are using a different table prefix than wp_ you have to change this, of course. If you are running WP-Piwik in multisite mode, you have to change the wp_sitemeta table. Not sure how to do this? Please contact your admin on further support.

I will post here if a Piwik or WP-Piwik update is available which fixes this issue.

Cheers braekling. It sucks for great developers like you when an API you’re using undergoes an abrupt unannounced change.

I really appreciate the wp-piwik contribution to Piwik: thanks for all your work in getting it working and keeping it working.

Thanks for the support braekling. I’ve not had any problems since switching back to http mode in the database. Also updated to Piwik 2.14.1 and still no issues. I’ll wait until Piwik gets the API sorted out before testing PHP mode again..

The Piwik team does a really great job and usually informs all developers about API changes.

But the issue discussed here seems to be a very speficic issue related to the PHP API and is not related to API changes… 2.14.1 solved it for most developers, but not for everybody.

Piwik has a lot of users with very different configurations. So, sadly, such issues can’t be avoided in all cases. If you look at the WP-Piwik support threads, WP-Piwik ran into such problems several times by my own error, too. And Piwik is much more complex than WP-Piwik.

So I appreciate your patience while the Piwik guys are working to resolve the issue. I know it’s annoying (me personal blog is affected, too), but they are doing their best.