Title: Wrong date field
Last modified: November 9, 2016

---

# Wrong date field

 *  Resolved [thinkero](https://wordpress.org/support/users/thinkero/)
 * (@thinkero)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/wrong-date-field/)
 * Hello,
 * After the update to 5.6.6.1, the dates of existing events are displayed in the
   second date field (“to” and not “from”). This field was empty before.
 * Also the calendar (when I pick a day) is in cyrillic alphabet.
 * I’m not able to publish any event.
 * The errror:
 * > Your event details are incorrect and cannot be published, please correct these
   > errors first:
   >  Dates must have correct formatting. Please use the date picker
   > provided.
 *     ```
       <p class="em-date-range">
       		From 					
       		<input class="em-date-start em-date-input-loc" type="text">
       		<input class="em-date-input" type="hidden" name="event_start_date" value="2016-12-15">
       		to		<input class="em-date-end em-date-input-loc" type="text">
       		<input class="em-date-input" type="hidden" name="event_end_date" value="2016-12-15">
       	</p>
       ```
   
    -  This topic was modified 9 years, 6 months ago by [thinkero](https://wordpress.org/support/users/thinkero/).

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Thread Starter [thinkero](https://wordpress.org/support/users/thinkero/)
 * (@thinkero)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/wrong-date-field/#post-8414976)
 * The situation occurs after updating GD Press Tools. It seems to be a conflict
   on that date picker js.
 *  Thread Starter [thinkero](https://wordpress.org/support/users/thinkero/)
 * (@thinkero)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/wrong-date-field/#post-8415012)
 * After installation of GD Content Tools 5.0.3, it seems that GD Content Tools 
   is overwriting some shared library / javascript / date selector dialog, affecting
   the functionality of Events Manager data picker.
 *  [caimin_nwl](https://wordpress.org/support/users/caimin_nwl/)
 * (@caimin_nwl)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/wrong-date-field/#post-8415634)
 * Thanks for the info, this might something worth mentioning to GD Content Tools.
 *  Thread Starter [thinkero](https://wordpress.org/support/users/thinkero/)
 * (@thinkero)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/wrong-date-field/#post-8416019)
 * I’ve already done that. I’m waiting for an idea to solve this from the both sides.
   Somehow, the fields of event dates (to-from) or just the date formats are affected
   and I’m not able to save/publish the events.
 *  [caimin_nwl](https://wordpress.org/support/users/caimin_nwl/)
 * (@caimin_nwl)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/wrong-date-field/#post-8416533)
 * Assuming that Events Manager works correctly until GD Content Tools is activated,
   then the issue is caused by something within that plugin and therefore is an 
   issue they’d need to look at.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Wrong date field’ is closed to new replies.

 * ![](https://ps.w.org/events-manager/assets/icon-256x256.png?rev=3550347)
 * [Events Manager - Calendar, Bookings, Tickets, and more!](https://wordpress.org/plugins/events-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/events-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/events-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/events-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/events-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/events-manager/reviews/)

## Tags

 * [date picker](https://wordpress.org/support/topic-tag/date-picker/)
 * [event dates](https://wordpress.org/support/topic-tag/event-dates/)

 * 5 replies
 * 2 participants
 * Last reply from: [caimin_nwl](https://wordpress.org/support/users/caimin_nwl/)
 * Last activity: [9 years, 6 months ago](https://wordpress.org/support/topic/wrong-date-field/#post-8416533)
 * Status: resolved