We should record some settings and preferences in all reports.
List of settings to remember & restore:
Currently, the dashboard remembers which "view types" you look at, and then restore it the next time you visit.
It would be interesting indeed to generalize the Dashboard setting save to all Piwik reports, ie. all Piwik reports would remember the last state they were in
Maybe worth a different ticket, but exclude low filter should be based on the total of the datatable column itself, rather than visits, in case report is a subset (of page category, visitor plugins, etc.).
updated ticket description to include all settings to restore as per comments
selected metrics in dashboard widgets are now stored in layout, too. also implemented some parts simplifying implementation of #3011 and #1915 and a small suggestion of #2461
Benaka what do you think is left on this ticket?
it would also be nice to have an JS api or function for core&plugins to use to record settings.
It was also reported in: #3369 and request in the forums few times.
Remembering these settings would make using Piwik a lot slicker and more user friendly. Please include it in a future edition!
This was also reported in #3469 Visits Overview (with graph) does not remember its status
It was reported in: #3807 Save and retrieve last zoom settings for maps
That we could also save & restore the map zoom. Is this a good idea (not sure)?
In 97f500fe247a88455bab6e72f5c8c06ee3029be7: refs #1915 a first version of persist & restore report settings. not everything is saved yet (such as metricsToPlot) but most things are
In ee2ec2b60a15007e971090d729945e3e870376a3: refs #1915 reset viewDataTable parameters before each test run to remove previously persisted viewdatatable params from other test runs
In d5091534263cc61c84d1feaea29c1e26f2e16929: refs #1915 added missing method to delete all viewdatatableparams, metricsToPlot should be saved now as well
Regarding "In Goals report: remember which subreport was clicked in the bottom left selector (eg. websites VS custom var VS etc.)"
As this is not a viewDataTable / Visualization I won't implement this (for now)
In ce33725096d27114303c89d5b045ba09c49b6ce6: refs #1915 trying to fix the installation tests
In 80d8d01e06650fc2699b2b99daafbe7bed3a4c26: refs #1915 persist selected metrics and rows in referrers evolution
In d9512c63af0495b8ddf6cd42f05939d8ebf95a4b: refs #1915 clear a users saved parameters on delete, added some tests
In 2035f17181da7704ea995c6c0131d68f64ff2e33: refs #1915 ignore filter_sort_order in change check after data requested
In ce761538aa479ecd893509cafe078b5461295e8b: refs #1915 make sure the flat param is set in the url even if the value is 0. Otherwise there a persisted preference saying flat=1 might be preferred. By making sure the flat param is present in the url the persisted value will be overwritten
Closing this for now. We can create new tickets in case we want to persist more parameters/settings/...
Nice work Thomas, this will be a super useful feature to most piwik users.
If you're using Piwik and have any feedback about this feature, please comment here
See also: #5162: Remember detailed visitor log 'Rows to display'
(Visitor Log footer does not store settings)
In 1de1cdb000d76c2632449fe4b8799270cd6c35a2: refs #1915 "columns" is added as a special query parameter in ViewDataTable class which results in having to do this. Problem: Switching to treemap visualization in eg PageUrls will save a columns "nb_hits" param, loading the normal view and sorting by column will result in only displaying nb_hits column instead of all columns. This seems to be the only case. If there are more we need to let the visualization decide which parameters to reset in case of a visualization change