Archiving custom range is not triggered correctly.
|Reported by:||p.banaszczyk||Owned by:||mattab|
|Priority:||normal||Milestone:||1.12 - The Great 1.x Backlog|
|Component:||Core||Keywords:||range, custom period, browser trigger|
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
[2013-03-15 15:29:38] [35d4e34d] [13.66 Mb] * ARCHIVING DISABLED, for Preparing archive: range(From 2013-03-12 to 2013-03-13), plugin VisitsSummary , Visits = <br/>
what shouldn't happen for period range.
In attachment patch that should solved this issue.