Use date_Create that does not throw exception or warning #2340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
This is inspired by Automattic#113
It seems that
new \DateTime( $meta_value, \wp_timezone() );
throws not only exception but also aE_WARNING
in certain cases.There is the
date_create
alternative, that according to manual is an alias. While testing it though, I found that, it returns false on failure and does NOT throw an exception or warning (as far as I can see).There are already unittests covering this function that are passing and also testing on the local dev-environment results in good results.
Alternate Designs
Benefits
Possible Drawbacks
Verification Process
Checklist:
Applicable Issues
Changelog Entry
Changed - Meta parsing tweak to avoid
E_WARNING
s