Title: Local time bug
Last modified: August 31, 2016

---

# Local time bug

 *  Resolved [Denis Bolvinov](https://wordpress.org/support/users/dinisiy/)
 * (@dinisiy)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/)
 * Hi, Will! I have noticed another bug: while post is schelduled in proper time(
   in wordpress admin), the real time of publication is wrong. This is because of
   default time settings are fixed to UTC+0.
 * For example, if I have time slot in plugin at 13:00, and wordpress setting UTC
   +3, the publication time will be 16:00…
 * [https://wordpress.org/plugins/automatic-post-publishing-scheduler/](https://wordpress.org/plugins/automatic-post-publishing-scheduler/)

Viewing 15 replies - 1 through 15 (of 16 total)

1 [2](https://wordpress.org/support/topic/local-time-bug/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/local-time-bug/page/2/?output_format=md)

 *  Plugin Author [Will Brubaker](https://wordpress.org/support/users/willthewebmechanic/)
 * (@willthewebmechanic)
 * Automattic Happiness Engineer
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6946939)
 * Thanks for the report. I’ll be looking in to it.
 *  Thread Starter [Denis Bolvinov](https://wordpress.org/support/users/dinisiy/)
 * (@dinisiy)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947074)
 * One more thing, that looks more like feature request.
 * When I publish many posts at the same time, posts are schelduled into the same
   slot. Is there any way to put every new post to the next slot, making posts queue?
 *  Plugin Author [Will Brubaker](https://wordpress.org/support/users/willthewebmechanic/)
 * (@willthewebmechanic)
 * Automattic Happiness Engineer
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947076)
 * I’m unable to reproduce the time issue that you reported.
 * time slot config: [https://cloudup.com/cK-GkCOadvy](https://cloudup.com/cK-GkCOadvy)
   
   WordPress time setting: [https://cloudup.com/cKGD_ce130k](https://cloudup.com/cKGD_ce130k)
   scheduled for 13:00: [https://cloudup.com/cyEx81Khf0t](https://cloudup.com/cyEx81Khf0t)
 * are you sure something else isn’t interfering with the time setting?
 *  Thread Starter [Denis Bolvinov](https://wordpress.org/support/users/dinisiy/)
 * (@dinisiy)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947164)
 * Yes, I’m sure, bug appears on the next step: actual time when post is published
   differs from the time that is shown in schelduled time field.
 * In your example: while schelduled time is 13:00, in fact the post will be published
   only at 16:00… But in post meta the “published” time will mistakenly be set to
   13:00
 *  Plugin Author [Will Brubaker](https://wordpress.org/support/users/willthewebmechanic/)
 * (@willthewebmechanic)
 * Automattic Happiness Engineer
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947166)
 * Thanks for building my understanding…I’ll have another look.
 * On the other issue that you are reporting – how is it that you are publishing
   multiple posts at the same time? Is this via the Android client?
 *  Thread Starter [Denis Bolvinov](https://wordpress.org/support/users/dinisiy/)
 * (@dinisiy)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947167)
 * I meant not exactly the same time, but the same time period between two slots.
 * I have two time slots: at 18:00 and at 20:00.
    When I scheldule two posts at 
   17:20 and at 17:40, both posts are put into 18:00 slot. The best way would be
   to publish one post at 18:00 and the other at 20:00.
 *  [nata-lee](https://wordpress.org/support/users/nata-lee/)
 * (@nata-lee)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947205)
 * Hello,
 * I have the same issue with time like in the example:
 * > if I have time slot in plugin at 13:00, and wordpress setting UTC+3, the publication
   > time will be 16:00
 * Also I can’t schedule posts if my time configuration is not in the US format (
   F j, Y for date and g:i a for time) and also can’t set any exclusion date. The
   plugin just doesn’t work with local datetime format settings.
 *  [nata-lee](https://wordpress.org/support/users/nata-lee/)
 * (@nata-lee)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947215)
 * I checked in the database, post_date and post_date_gmt in the table wp_post for
   posts with the local time problem is the same. I don’t know why it happened.
 * I disabled the plugin and tried to change the sheduled time but post_date and
   post_date_gmt are still the same for old posts. For new posts values of post_date
   and post_date_gmt are correct.
 *  Plugin Author [Will Brubaker](https://wordpress.org/support/users/willthewebmechanic/)
 * (@willthewebmechanic)
 * Automattic Happiness Engineer
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947216)
 * Thanks for that additional information. I haven’t found any time to dig in to
   this yet, but I hope to have time this weekend.
 *  Plugin Author [Will Brubaker](https://wordpress.org/support/users/willthewebmechanic/)
 * (@willthewebmechanic)
 * Automattic Happiness Engineer
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947224)
 * 2.1.5 should have this time thing sorted out
 *  Thread Starter [Denis Bolvinov](https://wordpress.org/support/users/dinisiy/)
 * (@dinisiy)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947226)
 * Unfortunately, seems that it doesn’t work properly still… the same bug remains
 *  Plugin Author [Will Brubaker](https://wordpress.org/support/users/willthewebmechanic/)
 * (@willthewebmechanic)
 * Automattic Happiness Engineer
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947228)
 * 2.1.6 maybe…
 *  Thread Starter [Denis Bolvinov](https://wordpress.org/support/users/dinisiy/)
 * (@dinisiy)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947229)
 * Now it works! Thanks a lot!
 * Should I make a new ticket for automatically queueing posts?
 *  Plugin Author [Will Brubaker](https://wordpress.org/support/users/willthewebmechanic/)
 * (@willthewebmechanic)
 * Automattic Happiness Engineer
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947230)
 * Denis,
 * A new thread for a different problem would be my preference. Thanks 🙂
 *  Plugin Author [Will Brubaker](https://wordpress.org/support/users/willthewebmechanic/)
 * (@willthewebmechanic)
 * Automattic Happiness Engineer
 * [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/#post-6947231)
 * and can you get me a screenshot of the time slot configuration?

Viewing 15 replies - 1 through 15 (of 16 total)

1 [2](https://wordpress.org/support/topic/local-time-bug/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/local-time-bug/page/2/?output_format=md)

The topic ‘Local time bug’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/automatic-post-publishing-scheduler_a15a57.
   svg)
 * [Automatic Post Publishing Scheduler](https://wordpress.org/plugins/automatic-post-publishing-scheduler/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/automatic-post-publishing-scheduler/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/automatic-post-publishing-scheduler/)
 * [Active Topics](https://wordpress.org/support/plugin/automatic-post-publishing-scheduler/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/automatic-post-publishing-scheduler/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/automatic-post-publishing-scheduler/reviews/)

 * 16 replies
 * 3 participants
 * Last reply from: [Denis Bolvinov](https://wordpress.org/support/users/dinisiy/)
 * Last activity: [10 years, 4 months ago](https://wordpress.org/support/topic/local-time-bug/page/2/#post-6947232)
 * Status: resolved