This repository was archived by the owner on Mar 26, 2021. It is now read-only.
This repository was archived by the owner on Mar 26, 2021. It is now read-only.
When site has no GMT offset saved, the expiry datetime causes problems #52
Closed
Description
When the 'gmt_offset'
value is a number (which is pretty much everywhen), the DateTimeZone constructor complains that the number is not a valid timezone.
nprapi-wordpress/push_story.php
Lines 676 to 679 in 853a301
PHP Fatal Error: Uncaught exception 'Exception' with message 'DateTimeZone::__construct(): Unknown or bad timezone (-4)' in /plugins/npr-story-api/psuh_story.php:676'
- make plugin draw from
'timezone_string'
when'gmt_offset'
is unset, in functionnprstory_get_post_expiry_datetime()
and in functionnprstory_save_datetime()
provide fallback behavior for when those meta are not setadd test case that runsnprstory_get_post_expiry_datetime( $post )
with every valid GMT offset and with every time zone and with nothing set for either.- when running against every time zone, the list at https://secure.php.net/manual/en/datetimezone.listabbreviations.php will need to be wp_list_pluck'd to get the timezone_id value, and then will need to be sort/uniq'd.
Metadata
Metadata
Assignees
Type
Projects
Relationships
Development
No branches or pull requests
Activity
Move the DateTimeZone construction into its own separate testable fun…
benlk commentedon May 23, 2018
Timezones are not a specific GMT offset; we need a GMT offset for this. A better approach is described in #53 that makes use of WordPress's tools for converting timezones to GMT offsets.
kaylima commentedon Sep 18, 2018
TODO: Up to 2 hours for remaining testing for #53 .
benlk commentedon Sep 19, 2018
Automated tests for #53 pass.
Human-run tests for #53 should perform the following tasks: