“Google+ Events has inbuilt time in PDT – Pacific Daylight Time Zone, and when you create your Events it automatically shows your selected time and date according to PDT irrespective of your current Time Zone.Thus, leading to wrong date and time in Event Invitation. Further when invitation is sent to different Time Zone it changes automatically according to receivers Time Zone as registered in Google Account.”
I recently used latest Google+ Events to invite some of my friends for a buddy’s birthday party …what an amazing feature! Hell, lot of themes to choose from you can even use customized ones moreover, you can also share photos live with Party Mode… (read Google’s official blog post by Vic Gundotra, here, to know more about +1 Events) super exciting feature…
But be careful! before you send any invitation do a test at your end to ensure everything goes right… like me. I sent an invitation of friend’s birthday party, scheduled for 8th July at 7:00 PM, and there was a blunder!!!
Google+ Events has inbuilt time in PDT – Pacific Daylight Time Zone (not mentioned), and when you create your Events it automatically shows your selected time and date according to PDT, irrespective of your current Time Zone. Thus, leading to wrong date and time in Event Invitation. Further when invitation is sent to different Time Zone it changes automatically according to receivers Time Zone as registered in Google Account. You can see the date and time in my Calendar(image below) and compare to the invitation(above image) being sent from my side to others.
Check out the snapshot, the date and time in the Events nowhere gives you the option of selecting the Time Zone.
Those who are not in PDT will obviously select the date and time according to their Time Zone. Like I did, I selected 8th July at 7:00 PM, when others received the invitation the Time and Date was changed according to their Time Zone i.e. In India 9th July, 7:30 AM , In Singapore 9th July at 10:00 PM, and all mess.
So, those who are not living in PDT, be careful till the bug is fixed!