Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Lag in Dashboard Reporting #479

Closed
anonymous-matomo-user opened this issue Dec 19, 2008 · 5 comments
Closed

Lag in Dashboard Reporting #479

anonymous-matomo-user opened this issue Dec 19, 2008 · 5 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Milestone
RobotRock

Comments

@anonymous-matomo-user
Copy link

The issue in Ticket #417 unfortunately seems to be alive and well in 0.2.26.

I have confirmed that there are stats in the database for today but they are not showing up in the dashboard yet.

I have also checked to make sure that the conf/global.ini.php file has
time_before_archive_considered_outdated = 10

I even tried a clean install to see if I could get the problem to go away.

Prior to my reinstall I noticed that the stats seem to show up the following day. For example, I attempted some page views yesterday when I was attempting to debug this issue and they didn’t show in the dashboard yesterday, but today when I look at the stats for yesterday the stats are there. Hope that helps.

Any assistance would be greatly appreciated. Thanks.
@robocoder
Copy link
Contributor

Sounds like this is related to ticket #26 (see comment in ticket #318 re: default_day)

@anonymous-matomo-user
Copy link
Author

I have already changed the default_day from yesterday to today in the global.ini.php file and I haven’t altered the config.ini.php file.

@robocoder
Copy link
Contributor

Is there anything your server log files and/or browser (eg firefox error console) that might help narrow this down?

You could also send a URL and login info to hello@piwik.org.

@mattab
Copy link
Member

mattab commented Feb 11, 2009

jharshaw, we need more info to help you with this bug. please send your piwik URL, login & pwd to hello@piwik.org, and steps to reproduce. We’d like to fix this issue. Thanks!

@robocoder
Copy link
Contributor

From feedback in http://forum.piwik.org/index.php?showtopic=214 the cause is an un-/mis- configured timezone in php.ini.

This will be fixed programmatically as a side-effect of ticket #56 (see comment 2).
A workaround, if unable to modify php.ini, is to edit index.php and piwik.php to specify the local timezone via date_default_timezone_set().

@anonymous-matomo-user anonymous-matomo-user added this to the RobotRock milestone Jul 8, 2014
@mattab mattab added the wontfix label Aug 3, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Milestone
RobotRock
Development

No branches or pull requests
3 participants
@mattab @robocoder @anonymous-matomo-user