Well… it’s one of those things were I don’t want to promise it, but now that I’m thinking about it, I feel like I have to try to make it work.
All of this gets insanely complex because of discrepancies between how different calendar systems generate the datetime codes in the feeds, the ability of feeds to have different events assigned to different time zones, different dates when different timezones enter and leave Daylight Saving Time, differences between timezone settings in WordPress vs. the server OS, various PHP date formatting functions, timezone adjustments shifting events onto different dates (e.g. when it’s 2 AM on Saturday in England it’s 9 PM on Friday here in Minneapolis… except during the couple of weeks a year when one country is in DST and the other isn’t, and then they’re 6 hours apart instead of 5), it goes on and on.
Finally early this year I got all of that sorted out, but in doing so, I had to remove any options for customizing the displayed timezone —?right now the plugin uses the timezone of the feed itself, and that’s it.
I ended up having to write my own time formatting function because there was just no way to get WordPress or PHP functions to stop interfering with their own timezone adjustments, and it’s one of the most complicated functions in the entire plugin!
After all of this, I had resigned myself, at least for the time being, to just displaying the feed’s inherent timezone. But now that I’ve had some distance from it all, I might be able to go back with fresh eyes and try to add options to a) shift events to the timezone in the WordPress settings, if different from the feed, and b) let the user see the times adjusted to their own local time. It’s the shifting events to different dates based on the timezone that really complicates things still.
-
This reply was modified 4 years, 9 months ago by
room34.