Not sure if this will help since some others are reporting similar issues, but just make sure you double check all the timezone settings. The calendar will use the event timezone by default now so you can try changing it to the timezone of your site to see if it helps.
Thanks for the recommendation, Nick…it helped me see closer to the actual problem. I went back and made sure the time zones matched (they do). Then, I looked closer at the error. It is the wrong date…because everything is 10 hours after its actual time. If you click on the event, it opens in Google Calendar and has all the right information. So there is clearly a time zone issue between Google and Simple Calendar. Anyone with any recommendations of how to resolve this?
Hmm ok. SO the thing is that if you view it on Google then it will usually automatically be adjusted to your timezone. So it does appear to be a timezone issue. I will have to dig deeper to see if anything comes to mind or if I see any glitches.
In Google it’s not being adjusted. Google is set for correct time zone. WordPress is set to correct time zone. SC is adding 10 hours (which is a strange number…we’re UTC-5…no 10’s in the mix).
Marking this resolved!
I got this fixed. I had to rebuild my calendar from scratch, but it fixed the time zone issues!
It created a new problem (Date is right, but “Sat” appears above “Sun”, etc.), but I’ll open a new thread for that.
So just be recreating the calendar it fixed your timezone issues?
Yes. I verified that Google and my site both had correct time zone set, then created a new (identical) calendar. The new calendar is correct.
Ok cool. The day off by one issue should also be fixed in 3.0.2 that we just put out today as well. Thanks for the follow up!
I updated to 3.0.5 and it did not fix the issue. However, I installed the beta and now the problem is resolved.
I do regret to say that I now have a new problem. I don’t know if it is related, but I cannot go to the next month anymore (I have events planned in the next month).
Awesome thanks for the updates.
Is there anyone who is NOT having the issue in 3.0.5 willing to update to 3.0.6 to see if it still is correct?
After our 3.0.2 fix it worked for a lot of users but then other users started experiencing the problem at that point. I am just trying to make sure both sides are taken care of here.
Thanks!
@ole123,
There are other threads about this can you add your issue onto one of those?
@dennisclaes,
Not sure if it is related, was it working before? Try enabling the “Always Enqueue” option in the plugin’s advanced settings. If that doesn’t work then please open a new thread with your site, etc. so I can take a look.
Thanks a lot for you response and the tip. However, it still does not work. Anyway, I don’t think it’s really related. I’ll start a different thread about it.
