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
1. Making a request to any widget without specifying @columns parameter. e.g.: index.php?module=API&format=html&method=VisitsSummary.get&idSite=2&period=range&date=2011-10-01,2011-10-01 [see first screen shot]
It returns Visits = '4' and it's Ok.
2. Making request with incorrect @columns parameter. e.g.: index.php?module=API&format=html&method=VisitsSummary.get&idSite=2&period=range&date=2011-10-01,2011-10-01&columns=nb_act [see second screen shot]
It returns '0' and it's Ok as such a metric doesn't exist.
3. Making request without @columns parameter again (The same as in first step). e.g.: index.php?module=API&format=html&method=VisitsSummary.get&idSite=2&period=range&date=2011-10-01,2011-10-01 [see third screen shot]
It returns Visits = '0' and it's not Ok.
The reason for this bug seems to be quite complex, I hope someone else (i.e. matt ;-) ) can make sense of it...
Reproduce (don't do it on the demo since it breaks the archives):
...?module=API&method=VisitsSummary.get&idSite=1&period=range&date=2010-07-17,2010-07-18
...?module=API&method=VisitsSummary.get&idSite=1&period=range&date=2010-07-17,2010-07-18&columns=xxx
Observation: The second call somehow retriggers archiving, there are more records in the numberic archive table afterwards.
Possible point to start:
Piwik_Archive_Single::get
is asked for the invalid column.The text was updated successfully, but these errors were encountered: