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
Reservation Timezone not equal as Planning #15929
Comments
Ok so : date.timezone in php defines your defaut timezone for php In the application, Configuration > General -> which timezone did you defined ? Because, as you have activated the timezone feature, we should not be talking of "UTC-5" but location like Europe/Lisbon for example. Also, as default user timezone, what timezone do you use ? Configuration > General should be in the timezone you want to display by default To compare, as my GLPI is used by users in all the world : PHP : General Conf : Timezone : My conf is not perfect because i have only one entity but, so far, it seems to work (we are in test on this feature). Their may be a bug actually but the location of it is not easy to define |
Hi @keguira, Thanks for your reply,
In the application configuration It has the same:
And in my user profile, has the same:
|
This comment was marked as outdated.
This comment was marked as outdated.
Issue continues |
Code of Conduct
Is there an existing issue for this?
Version
10.0.10 and Cloud
Bug description
The actual time in the Reservation calendar is not showing as the same in Planning, in Reservations it looks like showing in UTC while my Planning is in UTC-5:
Calendar in Reservation:
Calendar in Planning:
Relevant log output
No response
Page URL
No response
Steps To reproduce
No response
Your GLPI setup information
Information about system installation and configuration
Server
GLPI constants
Libraries
LDAP directories
SQL replicas
Notifications
Plugins list
Anything else?
I have setup php apache and cli with timezone UTC-5:
And MariaDB timezone as well:
All of them with the correct timezone.
The text was updated successfully, but these errors were encountered: