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
Seems that custom period should is only metric that should be processed independently (regardless browser triggering is on/off)
In global.ini.php we can disable browser archiving for everything except custom period, what seems to be expected behavior (as custom period needs to be archived somehow)
The only time that the browser will still trigger archiving is when requesting a custom date range that is not pre-processed yet
In current version (1.10 and 1.11 - not sure how it worked earlier) after disabling browser archiving (high traffic page - we're using archive scripts to compute data) i had problems with getting correct results for periods
In 5700b37: Refs #3833 - Piwik_Period's toString method does not return the type of the Period and a "Array to String conversion" notice is triggered. So we use the getLabel accessor.
Seems that custom period should is only metric that should be processed independently (regardless browser triggering is on/off)
In global.ini.php we can disable browser archiving for everything except custom period, what seems to be expected behavior (as custom period needs to be archived somehow)
The only time that the browser will still trigger archiving is when requesting a custom date range that is not pre-processed yet
In current version (1.10 and 1.11 - not sure how it worked earlier) after disabling browser archiving (high traffic page - we're using archive scripts to compute data) i had problems with getting correct results for periods
what shouldn't happen for period range.
In attachment patch that should solved this issue.
Keywords: range, custom period, browser trigger
The text was updated successfully, but these errors were encountered: