Couple more period selector related improvements #12326
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
Changing what
piwik.currentDateString
is meant to contain. Before it held the date query parameter value, unless the period was a range, in which case it held the last date in the date range (so w/2011-01-01,2011-01-23
, the date would be2011-01-23
). Now it will contain the two dates for ranges. Note: not sure if this will have any effect on other plugins, but I think core plugins are safe. I noticed it's only used by the managecustomalerts controller.Supply the site's timezone client side for calculating now/today/previousN/lastN. Note: this works for now, but I'm not sure if this is the best way to supply site info to the client.
Remove blip when hovering over dates in the date-picker directive.
For sanity, handle yesterdaySameTime client side (handled same as yesterday, since the frontend doesn't care about the time of day for periods).