|
April 22, 2016 at 3:32 am
The timezone set in the WordPress settings is Denver to match MST where my client is located. If I am pulling directly from the database, than it is grabbing the exact DateTime that it shows in the database, not UTC,
Whilst it is grabbing the exact datetime from the DB, it is in UTC+0
Event Espresso stores ALL dates within the datebase in UTC+0 and then applies your current timeszones ‘offset’ (the time different between UTC and your timezone) when outputting the dates.
So looking at your last screenshot (direct dates/times from the DB) – https://goo.gl/CNq3s6
Event Start = 2016-04-22 00:30:00
Event End = 2016-04-22 02:30:00
Those are UTC+0 based timestamps meaning you need to apply the ‘offset’ for your current timezone.
Denver = UTC-6 (taking into account DST)
2016-04-22 00:30:00 – 6 hours = 2016-04-21 18:30:00
2016-04-22 02:30:00 – 6 hours = 2016-04-21 20:30:00
So when you apply the offsite of your current timezone to the UTC timestamps saved within the dates they show the correct dates/times:
Event start = 2016-04-21 08:30pm
Event end = 2016-04-21 10:30pm
As shown here: https://goo.gl/4rCsPK
Event Espresso does this for you when using the models, you can pull the primary datetime based on the event ID using:
$datetime = EEM_Datetime::instance()->get_primary_datetime_for_event( $eventid, $try_to_exclude_expired = true, $try_to_exclude_deleted = true);
Then depending on exactly what you want to do you can do:
echo $datetime->get_i18n_datetime( 'DTT_EVT_start' );
or
$datetime->e_start_date()
To echo the values, or to store them:
$event_start = $datetime->get_i18n_datetime( 'DTT_EVT_start' );
or
$event_start = $datetime->start_date()
Or use any of the other methods available on the EE_Datetime object to do this for you.
You can always install Kint and then wrap the $datetime variable within d(); to see what is available.
|
