Nico Klasens <[EMAIL PROTECTED]> wrote > I just wanted the same behaviour as it was before. Now it does not matter > where the server is. The clock on the client machine is the same as what the > wizard shows.
I don't agree that the behaviour is the same. Before "now" did mean "now", but this is not anymore the case. Before the new date would be translated from client timezone to a timezone independent representation, so you would get the time "now" for a new date. In the new situation this is not the case, you only get "now" if you are in the same timezone. > The dates stored in the database are in milliseconds. The data is timezone > dependent. Server timezone independency is more a general problem not only > the wizards. If we want to support this then a lot of things have to be > changed. The described situation does not occur often and it is probably > easier to change your data instead of the application. You can put the timezone in MMBase 1.7 time tags, so there is no server timezone dependency anymore in the representation. The only problem that remains is in the EditWizards. Changing your data is no option, because the data is stored timezone independent. Martijn Houtman
