You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Berlin enforces storing datetime values according to UTC/GMT. For WordPress, date/gmdate are essentially synonymous, making these functions easy to conflate.
A future version of validate_datetime() may implement its own time zone handler, as a way to internally override/verify the UTC result, but gmdate() here is a small step towards that.
Fixes#75.
* Column: In validate_datetime(), prefer gmdate() over date().
* Queries\Date: Prefer gmdate() over date().
Berlin enforces storing datetime values according to UTC/GMT. For WordPress, date/gmdate are essentially synonymous, making these functions easy to conflate.
A future version of validate_datetime() may implement its own time zone handler, as a way to internally override/verify the UTC result, but gmdate() here is a small step towards that.
This is a merge of upstream changes from WP_Date_Query.
Fixes#75.
Berlin expects to be working with datetime's in UTC.
WordPress sets the timezone to UTC using
date_default_timezone_set( 'UTC' )
.This isn't really a problem, but it could be if
date_default_timezone_set()
was ever called using anything butUTC
.The text was updated successfully, but these errors were encountered: