Hi Alexander,
unfortunatelly not ... the thing is the window is actually quite
intelligent, it tries to sleect the users timezone. But if you have not
timezone in the current user profile it won't work. We might add a hook to
choose the server's configurated timezone instead.
Sebastian
Ok.
But what I have to do?
I've take a look in the configurations and I have the following:
default.timezone = Etc/GMT--3
I'm not sure about what could be wrong with that.
I'm using Centos 5.5.
[]s
Alexander
Brazil
On 10 fev, 17:39, seba.wag...@gmail.com seba.wag...@gmail.com
wrote:
have
In the window in openmeetings where you write the invitations you have the
possibility to choose a timezone. Have you chosen any time zone in there?
There might be a problem with the default selection in that box if the users
time zone is not set or not available that leads to this issue.
Ok.
If I select a timezone the email is sent. Great.
But there isn't any default timezone selected.
So, if it is an endless invitation, the user will always get an
error.
Do you have any clue, to put this working? I mean, the default
timezone?
[]s
Alexander
Brazil
On 10 fev, 18:30,
I have commtied a patch to have a default selection and if everything fails
the server will use the default timezone.
http://code.google.com/p/openmeetings/issues/detail?id=1316#c4
But if the default selection fails it will just select the very first item
from the list of timezones. That might
Now maybe I'm asking too much for you,
but I just did the checkout.
but, of course the structure it's different.
First I've tried only to copy the file inviteMainWindow.lzx, but
seems the this file doesn't exist in the r3537 version.
So, I simply put all the checkout files in the /usr/src,
Alex,
you have no chance in running the code that way.
If you want to have an up to date copy use the nightly build system and
download a copy tomorrow:
http://i4demo.com/openmeetings/builds/
... or you need to checkout really everything and build it locally.
Sebastian
2011/2/10 alexanderff
IT WORKED!!
THANK YOU!
SOLVED!
The sad thing is that the first timezone (and consequently the
default) is Fiji/New Zeland, and not the braziliam timezone.
But I suspect that I can edit the /usr/src/om/webapps/openmeetings/
languages/timezones.xml,
and put the braziliam in the top of the list.
