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
Variable "themeStyles" does not exist.
in /var/www/html/matomo/plugins/Morpheus/templates/layout.twig line 25
A fatal error occurred
The following error just broke Matomo (v3.9.1):
Variable "themeStyles" does not exist.
in /var/www/html/matomo/plugins/Morpheus/templates/layout.twig line 25
Troubleshooting
Follow these steps to solve the issue or report it to the team:
If you have just updated Matomo to the latest version, please try to restart your web server. This will clear the PHP opcache which may solve the problem.
If this is the first time you see this error, please try refresh the page.
If this error continues to happen, we appreciate if you send the error report to the Matomo team.
Further troubleshooting
If this error continues to happen, you may be able to fix this issue by disabling one or more of the Third-Party plugins. If you don't know which plugin is causing this error, we recommend to first disable any plugin not created by "Matomo" and not created by "InnoCraft". You can enable plugin again afterwards in the Plugins or Themes page under settings at any time.
BeeLikedDBIP | uninstall
-- | --
MarketingCampaignsReporting | uninstall
Signup | uninstall
WooCommerceAnalytics | uninstall
The text was updated successfully, but these errors were encountered:
@Findus23 found the issue, 2 .txt files did not had right permissions, its funny alto how this found in the end another resolution. I fixed the permissions and upgraded again it worked.
@lohic you will have to check manually the permission. Do a shell basic script to check that for you, and just seek for any users outside the ones servicing matomo.
A fatal error occurred
The following error just broke Matomo (v3.9.1):
Variable "themeStyles" does not exist.
in /var/www/html/matomo/plugins/Morpheus/templates/layout.twig line 25
The text was updated successfully, but these errors were encountered: