Hi @grungepopp
This is indeed timezone related.
Is the date in the admin interface correct or does that change as well?
And how are you displaying this date on the page?
Cheers, Jory
The date changes in the admin interface. So when you add a new item (in this case a bid) and select a “close date” using the datepicker and put in whatever date and say 12pm, when you hit save, it saves as 5pm.
On the front end template, I was just using {@close_date}. For now, we added a custom date function to subtract 5 hours, so it’s actually {@close_date,pods_custom_date_format} at the moment.
We want the time to be 2pm. So we’re saving them as 9am and then custom formatting the template to subtract 5 hours back to 2pm.
It doesn’t appear like Pods has updated recently, so we were wondering if you’re using some built in WordPress functionality that changed with a recent update. Just spitballing there 🙂
Setting WP Admin > Settings > Timezone to GMT-5 as well as a few other timezones, then saving a date/time field in-between and viewing… didn’t change the display of the date/time field.
Date/time field stores as plain text, e.g., 2026-01-21 12:23:58 without any indication of timezone.
Because Pods isn’t storing additional timezone information in the field, and because display isn’t effected by site timezone unless added by a plugin or theme: if it shows as the correct date as text in wp_postmeta table, but displays differently in admin interface after save, there may be an additional plugin filtering date output.
Some functions in the codebase if related to the issue might include apply_filters on any date or meta hooks, strtotime(), set_default_timezone().
