Closed GoogleCodeExporter closed 9 years ago
Currently the raidplaner stores everything as UTC, i.e. there is no timezone
support at the moment. This will change with 1.0 as more and more players from
countries with more than just one timezone are using the raidplaner.
However - the topic is complicated and there have been several issues in the
past, so - could you describe your problem a bit more detailed? Is it a problem
between timezones or are you having issues inside the same timezone? What is
happening, and what so you expect to happen?
Original comment by arne.cl...@gmail.com
on 24 Jun 2013 at 6:13
We're trying to run off of the WoW server time (PDT), our raids begin at 6 pm
PDT. Because of the UTC offset no one can confirm for raid after 11 am PDT.
It's really just a lagging on our guildies issue, I was just hoping there was a
quick fix. I've attempted to set the times all over the place with a
date_default_timezone_set("America/Los_Angeles")
wherever I thought it might possibly adjust the time into consideration to no
avail.
We're not so much looking into making the timezones view correctly for each
user, just so much as we can set the guild calendar to recognize the correct
timezone of our server.
Original comment by bandr...@gmail.com
on 25 Jun 2013 at 3:21
[deleted comment]
So I'm understanding correctly, that you've defined your raid times to be PDT,
but your server is located in another timezone (6 hours difference) so the
server is closing the raids early.
One quick solution for this would be to set the raid locking time to -6 hours.
This will close the raid 5 hours after the server thinks it started.
I will start working on 1.0.0 somewhere this week. I'll start with this feature
so you can work of a branch until 1.0.0 is officially released.
Original comment by arne.cl...@gmail.com
on 25 Jun 2013 at 7:30
Integrated into 1.0.0 branch.
The system will use the timezone set on the user's pc/browser to convert all
dates to the current timezone.
I also integrated a possibility to override the timezone, but there is no UI
for it - yet - as there are about 40 different timezones by 196 different
names. Putting that in a usable form is quite a lot of work and daylight saving
times plus a quite stubborn javascript API prevented me from implementing that
for 1.0.0.
The plan is to give the user profile a settings tab with a timezone chooser
somewhere in the future (e.g. 1.1).
For the time being, users will have to fix their system's timezone if the times
are off.
Original comment by arne.cl...@gmail.com
on 6 Oct 2013 at 4:27
Original comment by arne.cl...@gmail.com
on 20 Oct 2013 at 7:55
Original issue reported on code.google.com by
bandr...@gmail.com
on 23 Jun 2013 at 9:04