@mactac,
Someone else has reported this but I am unable to reproduce the error. Are the UTC and local times a little down the page correct?
In fact, if you can check the server time. Is that UTC, local to you or something different again?
Thread Starter
mactac
(@mactac)
I used to have it set to default, but now I have it set to the correct time zone for my location.
When I set it for 9AM, here’s what I get:
Current UTC time is: June 2, 2012 @ 3:11 pm
Current blog time is: June 2, 2012 @ 8:11 am
Next email notification will be sent when your blog time is after: June 3, 2012 @ 9:00 am
When I reload, I get:
Current UTC time is: June 2, 2012 @ 3:12 pm
Current blog time is: June 2, 2012 @ 8:12 am
Next email notification will be sent when your blog time is after: June 3, 2012 @ 4:00 pm
Interestingly, when it was set to default (+0), it would revert to 5PM, now it reverts to 4PM all the time instead.
Thread Starter
mactac
(@mactac)
By the way, also I seem to remember someone talking about a “force email send NOW” link to send a digest right away, but I don’t see that anymore. Am I dreaming, or is this gone in this version, or am I thinking about something else? (I don’t think I’m thinking about the test email button)
Thread Starter
mactac
(@mactac)
Oh, also – it doesn’t matter if it’s set to hourly,daily, whatever, it’s always 4PM
@mactac,
There has never been a way to force sending of the digest email, only a resend the previous email button.
As for the time setting, it is ignored for hourly intervals. For intervals larger than that is should display correctly. I can only thinks its an issue about the local time on the server. You could try setting the time zone with ini_set in the wp-config.php file and see if that helps.
Thread Starter
mactac
(@mactac)
My time zone is set correctly in WordPress, should that not override anything set via ini_set anyways?
Thread Starter
mactac
(@mactac)
I set the timezone in ini_set, and it didn’t make a difference. I do notice however that it’s simply setting the time for next email 7 hours away from what I set it to. ie if I set it to 9AM, come up as 9AM< but when I refresh, it’s set to 4PM. If I set it to 10AM, it’ll go to 5PM.
Of course the really weirs thing is that it’s actually set correctly after I click submit, but reverts when I go back to the page a second time.
Thread Starter
mactac
(@mactac)
Now I’m not getting notifications sent at all.
Thread Starter
mactac
(@mactac)
I just donated, hoping that might help me out with this problem a bit 🙂
I’m happy to give you access to my server if that would help…
Thread Starter
mactac
(@mactac)
Here are my setting, the email just went out at 11:00 AM
Current UTC time is: June 5, 2012 @ 6:12 pm
Current blog time is: June 5, 2012 @ 11:12 am
Next email notification will be sent when your blog time is after: June 6, 2012 @ 6:00 pm
I’m the other person MattyRob mentioned as having this problem. Here’s my thread: http://ww.wp.xz.cn/support/topic/plugin-subscribe2-send-digest-notification-always-defaults-to-2pm
I’ve been testing the plugin lately and the problem is it gets mixed up when handling and reporting local time vs. UTC time. We noticed that the settings and launch times were always five hours off of the expected time. (We are 5 hrs behind UTC time in Iowa.)
Some things I learned:
- When you set the Send Digest Notification time, the plugin will assume you’re using local time. After a refresh or reload of the settings page, it will display the UTC equivalent.
- “Next email notification will be sent when your blog time is after:” should say “when UTC time is after”.
- Example: We had it set so it would send June 6 at 1am, but it sent on June 5 8pm (UTC -5 hrs).
This really confused us for awhile but I think this will help clear it up.
Thread Starter
mactac
(@mactac)
Fantastic Jeremy – thanks for the clarification. It looks like the behavior is the same for mine as well.
Cool. @mattyrob, could be useful for the next version of your plugin.
Thread Starter
mactac
(@mactac)
It looks like the behavior of mine isn’t like yours. I set my time to send so that the UTC time was 30 min prior to the “Time to send”, and nothing went out 30 min later.
In fact, nothing has been sent in the last 2 days.
arrrgh.
