New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dashboard broken by 4.9.0 browser incompatibility #19109
Comments
Thanks for reporting this @mskala. We will release a patch fix for this issue in Matomo 4.9.1 shortly. Please also note that Firefox 76 reached end of life more than 5 months ago. I'd recommend upgrading your browser if possible. |
Cold, dead fingers. |
Even worse, the extended support release Firefox ESR 78 reached end of life five months ago. Firefox 67 (used by the issue opener) is no longer supported since almost three years (!). There are so many reasons to update the browser: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/ Accoording to https://caniuse.com/?search=replaceAll all browsers with exception of the Internet Explorer support String.replaceAll. The Internet Explorer is no longer supported since Matomo 4.6. So I don't think Matomo should include a polyfill for that. If someone is still using a three years old browser, well… it's the own fault. |
I don't think a Web site statistics system should depend upon running Javascript in order to display statistics at all, much less specific Javascript features of some recent browsers. Web site statistics are data, not code. But that's not really relevant here. What is relevant is that Matomo worked in my installation before 4.9.0; it doesn't work in 4.9.0; either it'll start working again, or I will stop using it; and I filed the issue in an effort to help, if the development team agrees that having it continue to work is desirable. Why I am unwilling to use a more recent browser is not relevant to the issue and although I can write at length on that topic, I don't think a discussion of it would be helpful to Matomo development. I won't participate in such a discussion here, though comments by others about it will certainly bear on my interest in continuing to use or help Matomo. |
I agree here and the access to the data itself is not locked behind Javascript at all. All data in Matomo is accessible via the reporting API and with the E-Mail reports even most graphs can be accessed as server-rendered images.
With the change of #19110 Matomo has already started working here in this case. So the only thing missing is a patch release including that fix and that should arrive soon.
I think a discussion about this is helpful in that it helps on how to make the decisions of "Which browser versions will Matomo officially support, which versions will not be intentionally broken and fixes will be accepted and which versions are too old and supporting them would harm too much other work (e.g. in making things less secure for other users)". |
This issue has been mentioned on Matomo forums. There might be relevant details there: |
Expected Behavior
Expected to be able to use the Matomo dashboard normally in Firefox version 67 after updating to Matomo 4.9.0.
Current Behavior
Blue header on dashboard displays normally, but page is otherwise blank. All links in the header have same broken behaviour, displaying header but nothing else, except that on the configuration page, the sidebar ("personal/system/privacy/etc.") displays in addition to the header.
Browser console displays these error messages:
Possible Solution
Remove the call to replaceAll that was introduced to source file "plugins/Morpheus/javascripts/piwikHelper.js" by commit afbe9c2 . Reverting that commit on my local copy, and removing the cached file "tmp/assets/asset_manager_core_js.js" which seems to be generated from that one, seems to fix the problem with no obvious downside. Presumably, whatever this commit was intended to solve will remain unsolved without the call to replaceAll. Some other way of replacing the percent signs (possibly just "replace") might be appropriate.
Add an automated test to make sure future versions will not be released containing calls to replaceAll.
Add a policy of human testing with an older browser on release candidates before releasing them.
Add a policy that a browser-breaking change will not be made without both warning users of the change and providing a path to opt out of the change.
Steps to Reproduce (for Bugs)
Context
This bug makes the Matomo dashboard/admin interface impossible for me to use at all. Independently of the technical issue, the fact that this occurred without warning on a routine update, creating emergency downtime for my business, reduces my trust in Matomo and my likelihood of buying any further services from the Matomo organization in the future.
Your Environment
The text was updated successfully, but these errors were encountered: