Custom Date Fields & CRED Expiry Field

This thread is resolved. Here is a description of the problem and solution.

Problem: Even though the post expiration timestamp in the database is identical to a custom field timestamp in the database, they are displayed on the front-end as different times.

Solution: Custom fields are assumed to be entered as GMT, and will be displayed as GMT. Post expiration is assumed to be entered as local time, and will be displayed as local time. Unfortunately there is no simple workaround right now.

This support ticket is created 4 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-	-
13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-	-

Supporter timezone: America/New_York (GMT-04:00)

Tagged: Toolset Forms

This topic contains 4 replies, has 2 voices.

Last updated by julieP 4 years, 7 months ago.

Assisted by: Christian Cox.

Author

Posts

April 14, 2020 at 11:34 am #1585113

julieP

The timezone for my site is set to London. I don't wish to change this because date/time information in wp-admin needs to be actual timezone (I don't want to have to remember to deduct an hour during summertime). I have a Types custom date field to record/display the date in date/time format. The CRED expiry field also displays in date/time format. Why is it that even when the timestamp in both these fields in the database are the same, the CRED field displays the time as an hour later? This doesn't make any sense.

April 14, 2020 at 8:57 pm #1585993

Christian Cox

Hi, yes I agree it's quite confusing. The simple explanation is when a post is saved, the custom field is assumed to be saved as GMT and will be displayed as GMT, while the expiration is assumed to be saved in WP local time and will be displayed as WP local time. The display here reflects that discrepancy, and unfortunately there's not a simple workaround right now.

April 15, 2020 at 6:05 am #1586243

julieP

Is it Toolset's intention to address it at some point though?

April 15, 2020 at 2:21 pm #1586957

Christian Cox

Yes I think the expiration and notification date systems need an overhaul in general, so if you'd like to see that happen sooner than later I suggest letting our management know by filing a request here: https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/

April 16, 2020 at 1:29 pm #1588459

julieP

Thank you - I'll do that!