Matomo fatal errors in 5.2.0 and now also 5.2.2
-
Hello. I have been having some issues with Matomo for the last two versions. Although they are different, it seems that they are related.
5.1.7 was working for me just fine.
When I attempted to upgrade to 5.2.0, it would cause a fatal error on the admin back end, but the site was still accessible to the public. Despite the WordPress fatal error saying that I’d get an email with details, it would never arrive. So I’d roll back to 5.1.7 and the issue would resolve – I could access the admin side, and Matomo worked again. I tried a few attempts to upgrade (both from the .zip and from WP) with the same results, so I just left it and waited for Matomo to be updated to see if that would solve it before reaching out for help.
5.2.2 arrived so I thought I’d try and update it. This time it didn’t throw the whole admin side into a fatal error, so that’s good. But Matomo is still broken. I can access the Matomo diagnostics page, but that’s about it. The summary page DOES throw a fatal error, and thankfully this time I do get an email with some details. The diagnostic page also shows a red error:
Matomo System Check Failed to run Matomo system check. You must be logged in to access this functionality.
I am, of course, logged in as an administrator, but Matomo doesn’t seem to think that I am. The Matomo settings are inaccessible.
I am getting an occasional fatal error in other areas of the admin area, but a refresh seems to let me resume, unlike the full-on fatal error of 5.2.0
The error email reads:
Error Details ============= An error of type E_ERROR was caused in line 117 of the file /home/execulin/public_html/wp/wp-content/plugins/matomo/app/core/API/ApiRenderer.php. Error message: Uncaught Exception: Renderer format ‘console’ not valid. Try any of the following instead: . in /home/execulin/public_html/wp/wp-content/plugins/matomo/app/core/API/ApiRenderer.php:117 Stack trace: #0 /home/execulin/public_html/wp/wp-content/plugins/matomo/app/core/API/ResponseBuilder.php(40): Piwik\API\ApiRenderer::factory() #1 /home/execulin/public_html/wp/wp-content/plugins/matomo/app/core/API/Request.php(252): Piwik\API\ResponseBuilder->__construct() #2 /home/execulin/public_html/wp/wp-content/plugins/matomo/app/core/API/Request.php(511): Piwik\API\Request->process() #3 /home/execulin/public_html/wp/wp-content/plugins/matomo/classes/WpMatomo/Report/Metadata.php(40): Piwik\API\Request::processRequest() #4 /home/execulin/public_html/wp/wp-content/plugins/matomo/classes/WpMatomo/Report/Metadata.php(75): WpMatomo\Report\Metadata->get_all_reports() #5 /home/execulin/public_html/wp/wp-content/plugins/matomo/classes/WpMatomo/Admin/Summary.php(116): WpMatomo\Report\Metadata->find_report_by_unique_id() #6 /home/execulin/public_html/wp/wp-content/plugins/matomo/classes/WpMatomo/Admin/Summary.php(65): WpMatomo\Admin\Summary->get_reports_to_show() #7 /home/execulin/public_html/wp/wp-includes/class-wp-hook.php(324): WpMatomo\Admin\Summary->show() #8 /home/execulin/public_html/wp/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #9 /home/execulin/public_html/wp/wp-includes/plugin.php(517): WP_Hook->do_action() #10 /home/execulin/public_html/wp/wp-admin/admin.php(259): do_action() #11 {main} thrown
I have done a few things to try and troubleshoot this, including:
– re-installing the plugin via .zip
– clearing the Matomo cache
– clearing the LSCache
– updating PHP from 8.3 to 8.4If anyone has any possible next steps for me, I would appreciate the help, and would love to get to the bottom of this. Thank you in advance.
- You must be logged in to reply to this topic.
