Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When manually entering a date, can't use 2-digit year #5368

HmCody opened this issue May 3, 2019 · 1 comment


None yet
1 participant
Copy link

commented May 3, 2019

Describe the bug
When I manually enter a date in a date field rather than picking with the calendar, if I enter 12/1/19, the date selected is 12/01/0019 rather than 12/01/2019. If I enter the full 4-digit year, everything is fine.

Not a big deal, but most software assumes the 4-digit if it is not typed to start with "20" so this requires remembering that it is different.

Pods Version


WordPress Environment

WordPress Version: 5.1.1

PHP Version: 7.1.28

MySQL Version: 5.5.5

Server Software: LiteSpeed

Your User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.131 Safari/537.36

Session Save Path: /opt/alt/php71/var/lib/php/session

Session Save Path Exists: Yes

Session Save Path Writeable: Yes

Session Max Lifetime: 1440

Opcode Cache:

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

APCu: No
Memcache: No
Memcached: Yes
Redis: Yes
WPDB Prefix: wpt8_

WP Multisite Mode: No

WP Memory Limit: 40M

Current Memory Usage: 34.727M

Current Memory Usage (real): 36.000M

Pods Network-Wide Activated: No

Pods Install Location: /home/thecodyg/

Pods Tableless Mode Activated: No

Pods Light Mode Activated: No

Currently Active Theme: Astra Child

Currently Active Plugins:

Current Year and Copyright Shortcodes: 1.0.2
Duplicate Post: 3.2.2
Ele Custom Skin: 1.0.9
Elementor: 2.5.14
Elementor Pro: 2.5.6
Loginizer: 1.4.1
Pods - Custom Content Types and Fields: 2.7.12

Possible Workaround
Type the 4-digit year.


This comment has been minimized.

Copy link

commented May 3, 2019

Issue-Label Bot is automatically applying the label Type: Bug to this issue, with a confidence of 0.89. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the Type: Bug label May 3, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.