we sometimes will have to push conversion data for days in the past.
Currently, such conversions will be tracked however old days reports will not be updated the next time they are requested.
When such conversions happen in the past, we should set a flag that will force this report to be refreshed the next time it is requested, or the next time archiving runs.
This function would also work for "updating" orders in previous days (which would invalidate past reports)
See also duplicated #2328
If visitors are recorded before the creation date of the website, should we record it in the past? If so, then we should also update the "website.ts_created" field when this happens (note: make it efficient).
When registering orders with revenue=0, what happens? SQL must ignore these when archiving?
See #1052 - we should implement this. When Cron not setup, the "delete invalid date" logic should be triggered from the browser triggered archives. Otherwise, when cron is running,
Why this ticket?
AWStats/Urchin alternative script #703 will push server log data to Piwik for days in the past, sometimes users will play logs from the last 3 months at once, or in several go, processing dates in random orders, websites in random order.
The goal is to accommodate this use case in a user friendly manner: Piwik should transparently force reprocessing for the websites/days/weeks/months/years where new Data was inserted.
SELECT count( idvisit ) , DATE( visit_last_action_time ) AS date, idsite FROM piwik_log_visit WHERE idvisit >4000000 GROUP BY idsite, date
This should work!
(In ) Fixes #2584
(In ) remove debug Refs #2584