Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Evan Herman

    (@eherman24)

    Hi Sarah,

    I’ll look into the issue shortly. What did you change the timezone setting too that triggered the error? If you changed it to one of the offset options, you may want to try changing it to one of the country/city options. It looks like the UTC options are triggering the error. I’ll look into this in the next release.

    Thanks,
    Evan

    Thread Starter Peetey18

    (@peetey18)

    I set it to: Manual Offset UTC-5. Thank you for looking into this.

    Thread Starter Peetey18

    (@peetey18)

    Hi Evan,

    I fixed the issue by setting my timezone settings to a nearby city. For some reason setting a UTC time caused the error, if that’s helpful.

    Thank you,
    Sarah

    Plugin Author Evan Herman

    (@eherman24)

    Hi Sarah,

    That is what I had recommended in my above post 🙂

    I am looking into the issue and why this may be happening. A fix should be included into the next release.

    I added that function to store the proper time based on the users timezone. It was using the global UTC setting of UTC-0 for the posts before the previous release.

    Thanks,
    Evan

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Notice: date_default_timezone_set() after changing timezone settings’ is closed to new replies.