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
It looks like time zones in published microformats2 values are currently ignored...? Looking at @sknebel's ("Anonymous"'s) and Scott Jenson's webmentions on https://snarfed.org/2023-10-30_51256#comments, their source mf2 both have dt-published values in UTC, ie they end with +00:00, but the plugin ignored that and uses their times directly in my WordPress's local time zone of Los Angeles (PT).
Specifically, here are the two dt-published values and source URLs:
The code pulls in the date and then formats it to store on the WordPress database.. which omits the timezone offset... but forgot to convert it to the site timezone.
It looks like time zones in
published
microformats2 values are currently ignored...? Looking at @sknebel's ("Anonymous"'s) and Scott Jenson's webmentions on https://snarfed.org/2023-10-30_51256#comments, their source mf2 both havedt-published
values in UTC, ie they end with+00:00
, but the plugin ignored that and uses their times directly in my WordPress's local time zone ofLos Angeles
(PT).Specifically, here are the two
dt-published
values and source URLs:2023-10-30 14:13:12.781417+00:00
2023-10-30T14:52:07+00:00
I don't know whether this regressed in 5.x or time zones were never supported at all. #415 is loosely related. Thanks in advance!
The text was updated successfully, but these errors were encountered: