> It appears that the list of the Editwizards shows time in de timezone of
the server and editing shows it in the timezone of the user, which is not
very consistent. At the moment I try to use for everybody in the world the
same time for an event at a certain location (presentation and editing). I
have now two choices:
         
> 1) cheat and show and edit time only in the server timezone 
> 2) save the timezone with the time and show and edit time in the right
timezone
         
> Presentation with MMBase 1.7 is no problem, but I have a problem with
editing time with the Editwizards. For 1) I have to change the Editwizards
to edit in the server timezone and for 2) I need to add timezone
possibilities to the Editwizards.   
         
> It looks a like standard problem to me that has to be in the Editwizards
anyway. Has anybody thought or done something about this or did I miss
something?
         
> Martijn Houtman


Hello Martijn,

You are right! The editwizards have a problem with editing the date and time
when the client is not in the same timezone as the server. That could also
explain the issue Michiel noticed, some time ago, that his linux and windows
machine had a one hour time difference.
The javascript code uses the Date object to get the numbers in the dropdown
boxes. The Date object calculates the numbers based on the Timezone of the
client machine. I hadn't looked closely into the date code of the
editwzards. I assumed that it was ok, because they already were patched a
lot of times.
I think, the only way to fix this is to send the numbers separately to the
client and not the UTC milliseconds. The getUTC** methods in javascript are
not the solution, because then the server has to use the date object in UTC
mode everywhere which will introdce many future headache. The server should
always be used to convert the UTC milliseconds to the separate numbers.
I don't have time to fix it now. So please add it to the bugtracker. I don't
think it is a showstopper for the upcoming release, but it is important
enough to be fixed before 1.7.1. 
 
Nico Klasens
 
Finalist IT Group
Java Specialists


Reply via email to