Timezone Correction: Nightmare in the making

  • seraph

    (@seraph)


    20 years, 4 months ago

    I was looking @ the timezone correction settings on my site, and adjusted it to match (I moved WP off my dev server to the production server). The posts were listing the old times still – I had not adjusted the timezone the first time.
    I then realized that it was statically rendering the dates per post! This is a potential nightmare, and I contend that NO correction is better than static correction.
    This should be quite easy to fix (I’ve done it before). As for upgrades, we can have the installer prompt the user for their currently set offset (or the one stored, after a confirmation) and the script can subtract the previously set static offsets. Then it will be compliant with current settings.
    Note: This will neccessitate that dates drawn from the DB come out GMT and nothing else.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Matt Mullenweg

    (@matt)

    20 years, 4 months ago

    I agree all datetime stuff should be stored in GMT. It’s just a matter of doing it.

    Thread Starter seraph

    (@seraph)

    20 years, 4 months ago

    *ahem* Would you like me to look into it?
    This would only involve posts, right? That shouldn’t be too difficult. After storing in GMT, I’ll edit the display stuff, and make that autocorrect. This will add a tiny amount of processing time required (per post/day). Not more than 0.01s on a page with 50 posts though (i tested this sometime last year).

    Alex King

    (@alexkingorg)

    20 years, 4 months ago

    Posts, comments and modification dates… I think. 🙂

    Thread Starter seraph

    (@seraph)

    20 years, 2 months ago

    I am starting to look into this, and quite likely will attempt to fix it in a backwards compatible manner
    oohhhh! the pain!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Timezone Correction: Nightmare in the making’ is closed to new replies.