Skip to content
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

Wrong date gets stored when in a different time zone #1813

dgsiegel opened this issue May 30, 2019 · 1 comment


Copy link

commented May 30, 2019

Describe the bug
I have a date field without time set up in a blueprint. When I input a date, it correctly gets stored in both the panel as well as in the txt file. However when my client (based in the UK) enters a date, the day after gets stored in the txt file and therefore in the panel as well. If we change his browser/system timezone to Europe/Berlin, this issue disappears.

To Reproduce
Steps to reproduce the behavior:

  1. Add a date field to a content type
  2. Change your system/browser timezone to UK or USA
  3. Enter a date
  4. Find that the date was changed to the day after

Expected behavior
The correct date should be visible.

Kirby Version

Desktop (please complete the following information):
Happens on different browsers, systems and even mobile devices, if they are set to a different time zone.

Additional context
Seems to be a similar issue:

@distantnative distantnative added this to the 3.2.1 milestone Jun 2, 2019

@bastianallgeier bastianallgeier modified the milestones: 3.2.1, 3.2.2 Jul 2, 2019

@bastianallgeier bastianallgeier modified the milestones: 3.2.2, 3.2.3 Jul 10, 2019

@bastianallgeier bastianallgeier modified the milestones: 3.2.3, 3.2.4 Jul 30, 2019

@bastianallgeier bastianallgeier removed this from the 3.2.4 milestone Aug 22, 2019


This comment has been minimized.

Copy link

commented Sep 15, 2019

Tried to reproduce using

But it works properly for me. Tried saving at date with time set to 23:00 as well as to 01:00 using America/Los_Angeles as time gone. Works properly in my tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.