Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
VanillaStats have flatlined after 2.2 upgrade
jamesinc
✭✭
Hey all,
Looking for some help debugging this one. Since upgrading to 2.2.1 (from 2.1.13) my vanilla stats charts have gone dead.
Weirdly, the page views chart hasn't gone to zero, but it has dropped by over 80%. Actuals remain unchanged, and Google Analytics also shows normal traffic to the site.
Has anyone else experienced this?
Edit: additional info - I also upgraded the DB to utf8mb4 to support Emoji. Not sure if this is of any relevance.
Tagged:
0
Comments
Did you perchance change your installation id in the
/conf/config.php
file?Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
Are you getting Javascript errors on pages? That
tick
event is fired asynchronously.@Linc, no, no JS errors to speak of. I can see a successful XHR to /settings/analyticstick.json
The thing that bends my mind the most is that I'm still getting a trickle of data for page views. The numbers look wrong - about 1/10 of actual views, but they're clearly actual numbers (they vary up and down day-to-day in an organic fashion).
@hgtonight have confirmed the installation ID and Secret in my config have not changed.
I solved it.
I have added
$Configuration['Garden']['Analytics']['Enabled'] = true;
to my config.Notes
I take that back. The graph has gone back to showing nothing. The return to normal you see in the graphic above has disappeared.
I'm now wondering if this is interference from a dev copy of the production site. In the past the dev site has never interfered with analytics, but I've disabled analytics on it anyway, and removed the installationID and secret just to be safe.
Confirmed: the issue seems to have been some kind of stats cross-talk from the dev copy of the site. Kind of strange that it started happening now when it had been setup this way since 2013.
There were some routing changes in Vanilla 2.2, so it's possible the server was relying on the software's previous non-standard behavior.