You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Posting this as much for reference (hello if you come here from Google) and to bring up a bad user experience.
In Matomo >= 3.8.0, if you don't read the release notes carefully, you might notice your Google Authenticator plugin was disabled. Okay, that's no problem, re-enable it. Everything looks fine on the admin panel, but tracking completely breaks!
I am unsure why calling Piwik\\Session::start() for tracking creates this error, and it led me down a rabbit hole of debugging our db connection before I realized the plugin connection.
Simply disabling the plugin fixed the issue.
It should probably not be possible to enable it on newer versions to prevent this.
The text was updated successfully, but these errors were encountered:
Thanks for letting us know.
AFAIK the latest version of GoogleAuthenticator has defined to not be compatible with 3.8 version and as such it shouldn't be possible to activate it (https://github.com/sgiehl/piwik-plugin-GoogleAuthenticator/blob/master/plugin.json#L10) . Did you maybe activate it again through the config file? In this case it shouldn't have been loaded AFAIK.
maybe you didn't have the latest version of Google Authenticator?
Posting this as much for reference (hello if you come here from Google) and to bring up a bad user experience.
In Matomo >= 3.8.0, if you don't read the release notes carefully, you might notice your Google Authenticator plugin was disabled. Okay, that's no problem, re-enable it. Everything looks fine on the admin panel, but tracking completely breaks!
The error is not obvious:
I am unsure why calling
Piwik\\Session::start()
for tracking creates this error, and it led me down a rabbit hole of debugging our db connection before I realized the plugin connection.Simply disabling the plugin fixed the issue.
It should probably not be possible to enable it on newer versions to prevent this.
The text was updated successfully, but these errors were encountered: