Hi there - thanks again for this great plugin. It's worked beautifully for the most part until I ran the upgrade last week.
I seem to be experiencing a 4-hour discrepancy somewhere within the system, and an issue with post expirations. In WordPress' General Settings area the time is correct.
When I create a new post and set the expiry date, as soon as I publish the post the expiry time changes - it displays a time 4 hours earlier than what I chose. The expiry time showing becomes 10:00, for example, if I choose 14:00.
I created a test post at 14:16 with the intention of test-expiring it at 14:18.
As soon as I saved the post, the expiry time visible in the Post Expirator box set itself to March 18, 2013 10:18. The debug log is showing this:
2013-03-18 14:16:26 6833 -> SCHEDULED at Mon, 18 Mar 2013 18:18:00 +0000 (1363630680) with options Array ( [expireType] => draft [id] => 6833 )
18:18:00 seems to indicate a 4-hour time difference.
In the cron schedule I see this: Mon, 18 Mar 2013 14:18:00 -0400 postExpiratorExpire
0 => 6833 Single Event
I have wp-cron disabled and the replacement cron job runs every hour. I set this to once per minute for the sake of testing, and the post expired at 14:18:00 even though it's displaying the wrong time in the post listing screen: March 18, 2013 10:18 am.
This may not be relevant, but my client pointed out: The Expires listing is now spelled out……April 1, 2013 instead of 04/04/2013, which isn’t that big of a problem, but the ones that have expired have not been marked draft.
These unexpired posts do expire if I set their expiry date to sometime in the near future, but ones with an older expiry date that has already passed are not being processed if I trigger the cron job.
This is happening on two different sites on the same server, with both regular posts and a custom post type. Any idea as to what may be the issue here? Thanks.