-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
issue with timezones #16
Comments
I have some problem , too !! |
I think, that it's not a problem with this bundle, but with configuration with your server. Check if server configuration is correct. |
Hi! I had the same problem. It was in ICU(International Components for Unicode) that used by php5-intl extension. You need to update ICU to fix it. |
Updating, ICU, doesn't seem to fix this issue. I've updated my OSes ICU library and php5-intl as well. On the client if I log the "changeDate" event for the datetimepicker, I'm getting a date -1 day to what I pick in the picker. The picker displays the correct chosen date, the event.date attribute is returning a different date. This varies depending on which "time" of the day I choose. Almost like it's trying to think for me which is not a desired behavior. Here's my datepicker init and event capture code, please let me know if there's a work around or if I have configured something incorrectly.
Thanks for any insight. |
Any news or advice on this? I think I have a similar issue with this: In the picker I choose 09:00 the object is set to 07:00:00, so GMT+2 is ignored, although php is correctly configured (date() shows the actual date). Further: despite the format, it seems to be the case, that the meridian is set? because i always get an invalid formField, if I pick a time after 12:00. |
@erne-mt , this remained an issue for me so I had to come up with a work around. I was able to just grab the value of the datetimepicker document element and that had the correct date, time and meridian, in my case something like: 2016-09-22 2:00 PM So, this works for me:
See if that works for you on the client-side. If you're using this in a Form and need to get the correct timezone in say your Controller, I had to actually force the timezone. I'm not sure what the bigger issue is, but this corrected it, and I haven't had time to dive deep.
Maybe this will help you. |
@kcaporaso thank you for your reply. This somewhat helped. But I still have the problem that the datefield will not accept a 24h format, e.g. 1400h is an invalid field. Any thoughts on that? |
So, I pick date for example 15.05.2015, but in controller I got 14.05.2015.
some code:
My timezone is 'Europe/Moscow'.
Any ideas?
Thank you.
The text was updated successfully, but these errors were encountered: