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 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.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.