Time Zone not respected, inaccurate stats result

  • I’ve been running this as a supplementary hits counter for years, and it’s always had the same problem — it stops counting for the day at midnight. It’s only 7pm for me, but the plugin moves to a new day. Already looked through the plugin; no settings or code for time zones.

    Why doesn’t it just respect the WP setting, which is and always has been set correctly on my sites? The daily stats are worthless because of this. Individual post hits (on All Posts screen) are all I can use.

    I understand not having a setting for that in the plugin. It needs to just follow the WP install settings.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author dFactory

    (@dfactory)

    Good point.

    We’ll look into this – try to replicate what you experience and adjust it if possible.

    Thread Starter btreece84

    (@btreece84)

    Good luck on that. I’ll screenshot it tonight if that helps. My server (Cloudways) runs UTC, but PHP and MySQL are set on my correct time zone. I’m based in the US, of course. Times are correct in WP set to my time zone. Not sure how you’d replicate it. It’s not UTC that I can tell. Changes days at 7pm for me right now, and we’re 6 hours behind (Central Time). Will change to 8pm with DST in March.

    • This reply was modified 9 months, 2 weeks ago by btreece84.
    Thread Starter btreece84

    (@btreece84)

    My bad. It is straight UTC. Started at 6pm today. Will start at 7pm in March.

    Thread Starter btreece84

    (@btreece84)

    Is it just me or is the $now variable not used after the weekly view in the dashboard class? My widget shows monthly, can’t change it, and everything in the monthly case is based on $time converting the period at the top of the block. Been through every file and can’t find the gmt_offset option being grabbed outside of dashboard_post_views_chart() in the dashboard class, nor any globals using $now.

    If I’m way off, I’ll shut up. Just digging out of curiosity.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Time Zone not respected, inaccurate stats result’ is closed to new replies.