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
in Graphs, selected metrics may not be saved and lost after a page reload #11499
Comments
@aimeos Are you viewing Piwik as anonymous user? It works for me if I'm logged in. |
@sgiehl No, I'm logged in too. Rearranging the dashboard is saved but not the metrics in the named panels. Can this be a problem rooted in the upgrade from Piwik 2? |
@aimeos hm... that's strange. could you try to create a new dashboard with those widgets on it and try if it works there? |
@sgiehl Same problem |
Can you please list exact steps to reproduce and what you get VS what you expected to see? Screenshot welcome too 👍 |
This is also broken on the demo.piwik.org but not in all widget types. (e.g. visits over time is running well, visits overview (with graph) is broken. Steps to reproduce:
|
Is this only about Dashboard? If not you might want to test #11983 and see if it changes anything |
Yes, the problem only appears on the dashboard (but only in some widgets). The PR at #11983 didn't fix it here. |
I guess the problem only occurs in widgets that contain multiple other "widgets". |
Same issue for me (worked in Piwik 2, just upgraded to 3, it doesn't save my metrics I want to plot, just those by default (eg Visitors and not unique visitors). As soon as I refresh the widget, it puts me back to the default metrics. |
@sgiehl maybe this is a regression we can address soon? |
Same issue here after upgrading from Piwik 2.x to 3.2.0. |
Seems fixed for me in |
Upgraded to 3.2.1 but still the same issue |
After upgrading from the last Piwik 2 to Piwik 3.0.2, selecting multiple metrics in the "Visitor Overview" and the "Goal Overview" aren't saved. After a page reload, only the default graph is shown again.
The text was updated successfully, but these errors were encountered: