Hello @sallijane Sorry to hear that you’re having trouble with your Matomo for WordPress. To be able to find a fix on this, could you please send us a copy of your system check report?
O.K., I just had a complex comment, but went to check on how to create a system report and lost it. GRR! Anyway, I had previously updated Matomo on this site: https://democracywatchnews.org, and yesterday was updating other plug-ins when this site, too developed a critical error. I had just updated PublishPress Authors, which is on your conflict list (not sure what to do about that, as I have used both plug-ins on all 4 of my sites). The reason I updated PublishPress Authors is this, from their change log, which made me think they might have resolved the issue:
Changed: Replaced Pimple library with a prefixed version of the library to avoid conflicts with other plugins; Changed: Replaced Psr/Container library with a prefixed version of the library to avoid conflicts with other plugins;
No luck though; Matomo is currently paused while the site is in Recovery Mode, so I cannot get a system report (will look to do so on uujec.net), but here is the message in the plug-in list:
This plugin failed to load properly and is paused during recovery mode.
An error of type E_COMPILE_ERROR
was caused in line 210
of the file /homepages/14/d4296767180/htdocs/wordpress/wp-content/plugins/matomo/app/vendor/php-di/php-di/src/Container.php
. Error message: Declaration of DI\Container::has($name) must be compatible with Psr\Container\ContainerInterface::has(string $id): bool
I avoid Google almost rabidly, and have been recommending Matomo in various WordPress groups since I found it, so I am a bit nonplussed to be having these issues; hoping it is my own lack of knowledge and not a major problem.
Of course, Matomo is deactivated on uujec.net, too—I was able to get an error log and test activity e-mail from Wordfence; would they be helpful? How do I get them to you?
-
This reply was modified 11 months ago by
sallijane.
Hello @sallijane The error you are getting is related to incompatible plugin with Matomo for WordPress. As of the moment, we do not have a workaround on this. However, our developers are working on it and might be resolved once Matomo for WordPress v5.0 is ready.
Thanks for the explanation! much appreciated
oops, forgot to mark as resolved (or technically, I guess, resolved-to-be)