Title: Failed to parse time string!
Last modified: May 4, 2018

---

# Failed to parse time string!

 *  Resolved [digicodex](https://wordpress.org/support/users/digicodex/)
 * (@digicodex)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/failed-to-parse-time-string/)
 * Hello,
    I’ve been having issues adding Date Post Type, here’s the error :
 * >  Fatal error: Uncaught Exception: DateTime::__construct(): Failed to parse 
   > time string (۱۳۹۷-۰۲-۱۴) at position 0 (�): Unexpected character in G:\xampp\
   > htdocs\..\wp-content\plugins\pods\classes\fields\datetime.php:668 Stack trace:#
   > 0 G:\xampp\htdocs\..\wp-content\plugins\pods\classes\fields\datetime.php(668):
   > DateTime->__construct(‘\xDB\xB1\xDB\xB3\xDB\xB9\xDB\xB7-\xDB\xB0\xDB\xB2-\xDB…’)#
   > 1 G:\xampp\htdocs\..\wp-content\plugins\pods\classes\PodsForm.php(1506): PodsField_DateTime-
   > >createFromFormat(‘m/d/Y’, ”) #2 G:\xampp\htdocs\..\wp-content\plugins\pods\
   > ui\fields\date.php(38): PodsForm::field_method(‘date’, ‘createFromForma…’, ‘
   > m/d/Y’, ”) #3 G:\xampp\htdocs\..\wp-content\plugins\pods\classes\PodsView.php(
   > 515): require(‘G:\\xampp\\htdocs…’) #4 G:\xampp\htdocs\..\wp-content\plugins\
   > pods\classes\PodsView.php(116): PodsView::get_template_part(‘G:/xampp/htdocs…’,
   > Array) #5 G:\xampp\htdocs\..\wp-content\plugins\pods\includes\classes.php(231):
   > PodsView::view(‘G:\\xamp in G:\xampp\htdocs\..\wp-content\plugins\pods\classes\
   > fields\datetime.php on line 668
    -  This topic was modified 8 years, 1 month ago by [digicodex](https://wordpress.org/support/users/digicodex/).
    -  This topic was modified 8 years, 1 month ago by [digicodex](https://wordpress.org/support/users/digicodex/).
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffailed-to-parse-time-string%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Contributor [Jim True](https://wordpress.org/support/users/jimtrue/)
 * (@jimtrue)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/failed-to-parse-time-string/#post-10247201)
 * That is a bug; we have an established process for reporting bugs from our FAQ:
 * >  If you’ve uncovered a Bug or have a Feature Request, we kindly request you
   > to create an Issue on our GitHub Repository at [https://github.com/pods-framework/pods/issues/new](https://github.com/pods-framework/pods/issues/new).
   > Please be very specific about what steps you did to create the issue you’re
   > having and include any screenshots or other configuration parameters to help
   > us recreate or isolate the issue.
 * Please report that at: [https://github.com/pods-framework/pods/issues/new](https://github.com/pods-framework/pods/issues/new)
 *  Plugin Contributor [Jim True](https://wordpress.org/support/users/jimtrue/)
 * (@jimtrue)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/failed-to-parse-time-string/#post-10247846)
 * Thank you [@digicodex](https://wordpress.org/support/users/digicodex/) for creating
   the bug report:
    [https://github.com/pods-framework/pods/issues/4896](https://github.com/pods-framework/pods/issues/4896)

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

The topic ‘Failed to parse time string!’ is closed to new replies.

 * ![](https://ps.w.org/pods/assets/icon.svg?rev=3286397)
 * [Pods - Custom Content Types and Fields](https://wordpress.org/plugins/pods/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/pods/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/pods/)
 * [Active Topics](https://wordpress.org/support/plugin/pods/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/pods/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/pods/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Jim True](https://wordpress.org/support/users/jimtrue/)
 * Last activity: [8 years, 1 month ago](https://wordpress.org/support/topic/failed-to-parse-time-string/#post-10247846)
 * Status: resolved