Appointment Field: Default time zone Europe/London GMT+1 instead of GMT

  • Profile Image
    ben.clarke10
    Asked on October 27, 2020 at 09:19 AM

    When someone books a slot the default time in the uk is currently going to GMT+1 which is wrong any way to set automatically to just GMT+0



  • Profile Image
    Basil_A
    Answered on October 27, 2020 at 10:17 AM

    Hi,

    You can change the default time by going to the settings of the appointment field and selecting the advanced tab.

    1603808115_5f982b73ef813_chrome_oRnMk6c6

    After that please scroll down to the default time option.

    1603808166_5f982ba64ee32_YRTqQ5CM38.png

    Please let us know if you require any further assistance.


  • Profile Image
    ben.clarke10
    Answered on October 27, 2020 at 10:23 AM

    That doesn’t seem to change what the person filling in the form sees - it wants to default to gmt+1 all the time

  • Profile Image
    Anita_K
    Answered on October 27, 2020 at 11:37 AM

    We apologize for the inconvenience. I've cleared your form's cache and now it should display the London (GMT) time zone. If the issue persists on your end, please try clearing your browser's cache or accessing the form from an incognito window.

  • Profile Image
    ben.clarke10
    Answered on October 27, 2020 at 12:05 PM

    That’s not working

    still showing gmt+1 which wrong

    1603814801_5f98459146885_EB3D6EB2-9FF2-4

  • Profile Image
    Anita_K
    Answered on October 27, 2020 at 01:26 PM

    Thank you for providing a screenshot. I tested this out on a new form and couldn't replicate the issue there. What I would suggest is that you try adding a new appointment field (you can hide the current one) and test it out to see if the default time zone is correct.

    Please give it a go and let us know if you're still experiencing the issue.

  • Profile Image
    Vick_W
    Answered on October 28, 2020 at 09:32 PM

    Hi Ben,

    This was escalated to the backend team. We've received a confirmation that the issue has been resolved. Can you please check this on your end again and let us know if the issue persists.

    Thanks.