pods Date / Time field format not recognized

Issue Overview

Entry in a Date / Time field can't be recognised when using with Date Format Type "WordPress Default".

The Webseite is German and the with WordPress Default uses the monthname: j. F Y

Expected Behavior

Datetime value should be saved but won't.

Current Behavior

WordPress Default Format and Custom format produce error

What I try to enter

error

Possible Solution

WordPress Environment

``` Debug Information WordPress Version: 4.9.6

PHP Version: 7.1.17-1+ubuntu16.04.1+deb.sury.org+1

MySQL Version: 5.7.21

Server Software: Apache

Your User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3451.0 Safari/537.36

Session Save Path: /var/lib/php/sessions

Session Save Path Exists: Yes

Session Save Path Writeable: Yes

Session Max Lifetime: 1440

Opcode Cache:

Apc: No Memcached: No OPcache: Yes Redis: No Object Cache:

APC: No APCu: No Memcache: No Memcached: Yes Redis: No WPDB Prefix: lawp_

WP Multisite Mode: No

WP Memory Limit: 40M

Pods Network-Wide Activated: No

Pods Install Location: /var/www/vhosts/lachevaline/releases/20180613125949/web/app/plugins/pods/

Pods Tableless Mode Activated: No

Pods Light Mode Activated: No

Currently Active Theme: lachevaline

Currently Active Plugins:

ARI Fancy Lightbox: 1.3.4 Disable Comments: 1.7.1 Duplicate Post: 3.2.2 Enable Media Replace: 3.2.5 GP Premium: 1.6.2 Gravity Forms: 2.2.5.21 Gridable: 1.2.2 Maintenance Mode: 2.4.3 Members: 2.0.2 Pods - Custom Content Types and Fields: 2.7.6 Recipe Custom Post Type: 1.0 Schema Pro: 1.1.3 The SEO Framework: 3.0.6 User Switching: 1.3.1 WordPress Importer: 0.6.4 WP Migrate DB Pro: 1.8.1 WP Migrate DB Pro CLI: 1.3.2 WP Migrate DB Pro Media Files: 1.4.9 WP Term Order: 0.1.4

</details>

## Pods Package Export (helpful!)
<!-- Please include the Pods Package Export as it will be helpful in reproducing your issues. -->
<!-- To access: Pods Admin, Components, Migrate: Packages, Enable. -->
<!-- Then Pods Admin, Migrate: Packages, Export and Copy and Paste the JSON here OR -->
<!-- Save to a text file and upload to this bug report -->


## Workaround or Alternate Solution Until Bug is Addressed
<!-- We will complete this section, or if you've already found a workaround, -->
<!-- you can add it here -->
Use a format with no monthnames but only numbers.

## Related Issues and/or PRs
<!-- List related issues or PRs against other branches:  -->

Jun 14 '18 14:06 zu

Similar issue #4925 (I think)

and yes could reproduce that! (applies to all non English settings I tested)

Aug 31 '18 11:08 quasel

Another one - #4814 but this time it's only about the output but I guess while you are at it…

Sep 01 '18 23:09 quasel

Just as an FYI, I spent some time today looking for a solution and wanted to share what I found:

The crux of the issue is that submitted dates are in the current user's locale.
Back-end validation fails since PHP date functions expect dates in English.
Converting a non-English date string to a timestamp or another locale requires PHP's Intl extension or a third party library (strptime() does not behave consistently from environment to environment and is not implemented in Windows at all).
Even if translated dates are validated correctly, they would still be stored in the current user's locale which will cause problems when you have multiple users with different locales so having a consistent storage format is a good idea (regardless of the input format).
IMO, the solution would be to use a consistent format (like ISO 8601) when submitting and storing dates and use alternative formats for display and user interaction (e.g. through jQuery Datepicker's altField and altFormat). The downside is that you must know the field's configured format when displaying the value in the front-end, for example. This is pretty much the way WordPress handles post dates.

Sep 29 '18 09:09 atanas-dev

The problem is still in Pods 2.8, with French date format, I cannot save the CPT, either with default Wordpress format, or custom (j F Y).

Dec 16 '21 17:12 sandrine-rodrigues

Hi @sandrine-rodrigues

I created a new issue to bundle related issues together.

Dec 28 '21 09:12 JoryHogeveen

Let's retest this after Pods 2.8.9 goes out as it has code that touches this logic.

Jan 27 '22 07:01 sc0ttkclark

Still the same issue after updating to Pods 2.8.9....

Feb 01 '22 21:02 sandrine-rodrigues

@sc0ttkclark This is a react / DFV issue, see: https://github.com/pods-framework/pods/issues/6389

Feb 28 '22 17:02 JoryHogeveen

Hi, I just solved this problem by enabling HTML 5 fields in the "Date Options". And the format is validatable by php and as I wish in the frontend.

Apr 08 '22 17:04 fhcoding

Hi, I just solved this problem by enabling HTML 5 fields in the "Date Options". And the format is validatable by php and as I wish in the frontend.

Unfortunately, I cannot confirm this. I have also enabled HTML5 and selected "WordPress default (j. F Y)" as the format. The website language is German. The date output is still English.

Dec 12 '22 10:12 trinermedia

HTML5 doesn't support various formats. The format is based on your browser mostly. On the front-end it should change to the selected format depending on how you use the field. Our functions and magic tags all output the formatted value.

#6860 fixed existing formatting issues with both the regular and HTML5 field and was merged into Pods 2.9.2.

Closing issue!

Dec 13 '22 17:12 JoryHogeveen

Ok, using the pods shortcode with the syntax for magic tags and the technique described here I could make it work. Thanks!

Jan 03 '23 14:01 trinermedia

pods pods copied to clipboard

Date / Time field format not recognized

Issue Overview

Expected Behavior

Current Behavior

Possible Solution

WordPress Environment

pods
pods copied to clipboard