Viewing 15 replies - 31 through 45 (of 47 total)
  • Not sure when it was broken. I have it set to auto update and this is the first time it was brought to my attention.

    Plugin Contributor Nick Young

    (@nickyoung87)

    Ok thanks for the info. I assume your event time, calendar time, and global settings timezone in Google is the same as that then also?

    Yes > https://cl.ly/3k2j2s0N311b
    (halifax & moncton are in the same time zone)

    Nick, so far so good for me! I seems the the two-day issues with “all day” events is fixed for me including the dates from Google’s US Holiday calendar. It was a good opportunity to force my calendar users to be more specific about event times anyway. ??

    It is probably worth noting prominently in the documentation about the multiple timezone settings. Some folks don’t know that you can set Google Apps in one timezone and use your plugin to display events in different timezones. I noticed that I had better luck in the previous version setting the timezone specifically for each calendar. BUT my test server had the calendars still set to use the WordPress timezone (default) and that is working fine as well.

    Plugin Contributor Nick Young

    (@nickyoung87)

    Thanks for the update Jess. That is on the beta2 version?

    I agree with you on the documentation and have started thinking about this as well. There are 5 places (that I know of) that you can change the timezone!

    Yes, everything I tested was with your Beta2 posted link.

    Hi Nick,

    after playing around with the time settings I cannot find a problem here. I get perfect results if I request eg. [start-date format=”d.”] @ [start-time format H:i], same for end-date/time. The time is shown exactly the way it should be – no shift or anything. The problem occures for whole day events only and if I request a [start-time] for whole day events I get 0:00 for the [start-date]-1 (!) and 23:59 for the [end-time] at the [end-date]-1.

    Not that I would have a clue, but how could this be a time zone issue?

    Thanks,
    Ole.
    P.S.: I am stilll on 3.0.9 beta 2 .

    Plugin Contributor Nick Young

    (@nickyoung87)

    Cool.

    here is some documentation we just put up. Please if you are having issues with this still check it out:

    https://docs.simplecalendar.io/timezone-settings/

    Nick,

    Thanks for the documentation – I’ve set both Google and WP calendars as per your instructions. I’m in Central TZ, so I’ve used Chicago.

    I’ve created a test event on the Google calendar that appears to be correct on my WP sites.

    https://www.visiblechild.org – uses the current NON Beta version (3.0.8)
    https://www.fhf-dev.org – uses the Beta release (3.0.9 beta 1)

    So I’m not sure if it was my timezone settings, or what it was, but right now BOTH sites are showing the correct day and time. My previous problem was that the calendar was showing the next day for today.

    I’ll check back later today to see if it’s still accurate.

    Thanks!

    Hi Nick,

    thanks for the documentation. I re-checked all settings. The problem remains unsolved for me.

    Best regards,
    Ole.

    Plugin Contributor Nick Young

    (@nickyoung87)

    @ole123,

    Can you provide me your calendar ID so I can use it for testing?

    @thale.mn,

    Glad to hear that! Please do let me know if anything weird starts to happen ??

    Hi Nick,

    here is the Cal ID: [email protected]

    regards,
    Ole.

    The new update seems to have fixed it for me. thanks.

    Hi Nick,
    just realized there is a new official update 3.0.9. After installing it the problem is gone. Everything back to the way it should be.

    Thank you,
    Ole.

    Thread Starter ctcka

    (@ctcka)

    Hi Nick

    I’ve installed the official 3.0.9 update and, like Ole, it’s fixed the one day off issue. Thank you! It doesn’t display events from multiple calendars though – but I’ll post a separate query for that.

    Mark

Viewing 15 replies - 31 through 45 (of 47 total)
  • The topic ‘3.0.8 update now one day off’ is closed to new replies.