Hi Matt, actually the request does have the token_auth...I just double checked. It's just not printed there.
Here's an actual request URL, with real values removed, to avoid confusion:
http://path/to/piwik/piwik.php?idsite=38&rec=1&url=http%3A%2F%2Fsitetobetracked.com&action_name=Home&rand=12&apiv=1&_idvc=1&res=1366x768&ua=Mozilla%2F5.0+%28Windows+NT+6.1%3B+WOW64%3B+rv%3A13.0%29+Gecko%2F20100101+Firefox%2F13.0.1&lang=en-us%2Cen&cip=11.22.33.44&cdt=2013-10-13&new_visit=1&country=us®ion=MI&format=JSON&module=API&method=CoreAdminHome.invalidateArchivedReports&token_auth=xxxx
I seem to get a successful response from the API, so also for that reason, I don't think there's an issue with the token_auth. The API request seems to be successful, and I see all of the info show up in the database. What doesn't make sense to me is why none of that data shows up on the GUI. I DID try to force Piwik to re-run its reports, and here are the steps I took. (I checked the GUI after each step to see if the problem was solved, but unfortunately, it was not.) Can you please let me know what I might be doing wrong?
1) Ensured that "Delete old logs" was OFF in the Settings area.
2) Deleted the archive tables from the database.
3) Made requests to the tracking API, using the param
&method=CoreAdminHome.invalidateArchivedReports to let Piwik know that the historical data I was
sending it was after the fact. (Tried also without this parameter, too.)
4) Ran the archive.php cron job.
Additionally, running archive.php suggests that Piwik doesn't recognize the historical data at all....even though that data came in through its own API. Here's a sample output from archive.php:
[2013-12-10 17:48:51] [xxxxxxxx] [3.34 Mb] Archived website id = 38, period = day, Time elapsed: 0.089s
[2013-12-10 17:48:52] [xxxxxxxx] [3.48 Mb] Archived website id = 38, period = week, 0 visits, Time elapsed: 0.729s
[2013-12-10 17:48:52] [xxxxxxxx] [3.35 Mb] Archived website id = 38, period = month, 0 visits, Time elapsed: 0.237s
[2013-12-10 17:48:52] [xxxxxxxx] [3.34 Mb] Archived website id = 38, period = year, 0 visits, Time elapsed: 0.166s
[2013-12-10 17:48:52] [xxxxxxxx] [3.33 Mb] Archived website id = 38, today = 0 visits, 4 API requests, Time elapsed: 1.223s [17/17 done]
Maybe there is another way to go about re-running reports? Perhaps the above process isn't enough? Any insight on this would be greatly appreciated.
Here's an actual request URL, with real values removed, to avoid confusion:
http://path/to/piwik/piwik.php?idsite=38&rec=1&url=http%3A%2F%2Fsitetobetracked.com&action_name=Home&rand=12&apiv=1&_idvc=1&res=1366x768&ua=Mozilla%2F5.0+%28Windows+NT+6.1%3B+WOW64%3B+rv%3A13.0%29+Gecko%2F20100101+Firefox%2F13.0.1&lang=en-us%2Cen&cip=11.22.33.44&cdt=2013-10-13&new_visit=1&country=us®ion=MI&format=JSON&module=API&method=CoreAdminHome.invalidateArchivedReports&token_auth=xxxx
I seem to get a successful response from the API, so also for that reason, I don't think there's an issue with the token_auth. The API request seems to be successful, and I see all of the info show up in the database. What doesn't make sense to me is why none of that data shows up on the GUI. I DID try to force Piwik to re-run its reports, and here are the steps I took. (I checked the GUI after each step to see if the problem was solved, but unfortunately, it was not.) Can you please let me know what I might be doing wrong?
1) Ensured that "Delete old logs" was OFF in the Settings area.
2) Deleted the archive tables from the database.
3) Made requests to the tracking API, using the param
&method=CoreAdminHome.invalidateArchivedReports to let Piwik know that the historical data I was
sending it was after the fact. (Tried also without this parameter, too.)
4) Ran the archive.php cron job.
Additionally, running archive.php suggests that Piwik doesn't recognize the historical data at all....even though that data came in through its own API. Here's a sample output from archive.php:
[2013-12-10 17:48:51] [xxxxxxxx] [3.34 Mb] Archived website id = 38, period = day, Time elapsed: 0.089s
[2013-12-10 17:48:52] [xxxxxxxx] [3.48 Mb] Archived website id = 38, period = week, 0 visits, Time elapsed: 0.729s
[2013-12-10 17:48:52] [xxxxxxxx] [3.35 Mb] Archived website id = 38, period = month, 0 visits, Time elapsed: 0.237s
[2013-12-10 17:48:52] [xxxxxxxx] [3.34 Mb] Archived website id = 38, period = year, 0 visits, Time elapsed: 0.166s
[2013-12-10 17:48:52] [xxxxxxxx] [3.33 Mb] Archived website id = 38, today = 0 visits, 4 API requests, Time elapsed: 1.223s [17/17 done]
Maybe there is another way to go about re-running reports? Perhaps the above process isn't enough? Any insight on this would be greatly appreciated.