Partly because of a warning I saw in Piwik, saying my PHP version 5.3 was EOL (end of life), my host upgraded the PHP version (for all his clients) (and upgraded a lot of other stuff too). Somehow, that broke my Piwik (but not anyone else’s Piwik, in his server farm).
It had stopped tracking, and instead of my usual dashboard, I saw some kind of error page, which allowed me to send a report to piwik. (maybe “crash” report, I don’t remember) At the time, I didn’t know my host was doing upgrades, so I sent the report, thinking it had died out of the blue. When I notified my host about the error page, that’s when he told me he was doing upgrades, including the PHP version. And it looks like he also upgraded Piwik, to 2.9.1.
Also, there were 2 errors showing on my System Check page – 1 critical, and 1 optional. For the optional one, it was File Integrity. Somehow, that got fixed, which caused my dashboard to come back, and Piwik started tracking again. (Although I’m not sure if it’s tracking properly.) The critical error is still showing, and my host hasn’t had time to work on it. So I thought there’s an outside chance I might be able to fix it myself, with your help.
So on System Check page, the critical error, under Other Required Extensioins, mbstring has the red X. And in bold red text, it says:
“The mbstring extension is required to handle multibyte characters in the User interface and API responses. Also please check that mbstring.func_overload is set to “0” in php.ini.”
And it’s repeated twice, for some reason.
The only other issue, is that my Geo Location option isn’t working. iir, I had set up PHP Geo Location. So I’m thinking I’ll reset that, after this error is fixed. Although I don’t know, maybe they’re related, and fixing one, will fix the other?
Does that sound like something I could fix? Or should I just wait until my host has time to fix?
Thanks for your help