Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties.
You can write credentials here just check PRIVATE Reply so nobody can see them except us.
This is most likely a time zone issue on your website.
Amelia doesn't have any time zone settings, and it relies on WordPress' General settings. Here's how it works:
All times in the back-end of Amelia will be shown exactly how you save them, so (for example) if your employee works from 09:00 - 17:00, or if there's an appointment from 09:00 - 10:00, that's how you will see them in the back-end.
If you enable "Show booking slots in client time zone" in Amelia's General settings, though, that may not be what your customers see, depending on where they're located, and what your WordPress site has been configured.
If this option in Amelia's General settings is disabled, all times on the front end will be the same as times in the back end. So, if your employee's work hours are from 09:00 - 17:00 in UTC+1, with this option disabled, regardless if your customer is in UTC+1, or in UTC+10 - they will still see times from 09:00 - 17:00, so if you have customers in multiple time zones, it's advisable to enable this option in Amelia's General Settings.
Important: In order for Amelia to store correct appointment times in the database (which is almost always in UTC time zone), you need to edit the WordPress time zone to show the city you're in (or the city in your time zone), like this:
This way, when Daylight Savings Time starts (or ends), the times will be adjusted accordingly and you won't have to worry about them anymore.
If you save your Time Zone in UTC+/- format, you may experience issues with Daylight Savings Time:
Explanation: When you configure the time zone to be "UTC+1" it will always be UTC+1. So, if we take Belgrade, Serbia as an example - without Daylight Savings Time, it is in UTC+1 time zone, but when Daylight Savings Time starts, Belgrade is in UTC+2. If you leave the time zone to be hard-coded to UTC+1, the times that your customers book on the front end will not be properly adjusted to what you see in the back end.
Example with UTC+1 configured: It is mid-summer, and Belgrade is in UTC+2. "Show booking slots in client time zone" is enabled, and a customer from Belgrade opens your website to book an appointment. The working hours of your employee are set from 09:00 - 17:00 (in UTC+1), but the customer sees them as 10:00 - 18:00. This is because the time zone is hard-coded in the back-end, while on the front-end it shows the time in UTC+2. So, a customer books an appointment for 10:00, and shows up at 10:00, while you expect to see them at 09:00.
Please note: If you hard-coded the time zone, and you have booked appointments, once you switch the time zone in WordPress to your city, it will adjust the times in Amelia's appointments to fit the time zone your city is currently in. This happens because (as mentioned above) the times are saved in UTC in the database, and it's adjusted in the plugin programmatically. So, if you have a hard-coded time zone set to UTC+1, and someone booked an appointment for 09:00, that time is saved as 08:00 in the database. When you change the time zone to your city (which is now in UTC+2), the appointment time will be adjusted to the time saved in the database 08:00 + 2:00, so the appointment time will switch to 10:00. The only solution, in this case, is to manually modify the appointment times, but it's the only way to make sure your time zone is properly configured, and that the future appointments will be saved and displayed correctly both for you and your customers on the front-end.
Summary: When you select the city you're in, in WordPress' General Settings, the system automatically calculates the Daylight Savings Time, and shifts the clock accordingly, so if you have any issues with what you see on the front end vs what you see in the back-end, always check the Time Zone in WordPress
A time zone issue, that is difficult to see; good tip.
I have checked the General Settings; the Timezone is set to a city (Brussels) so, not an issue there. I have also checked using the frontend while in the same timezone; so the backend and the front-end should be in sync? Given the times shown on the front-end is server time due to the setting "Show booking slots in client time zone" being turned off.
Do employee holiday hours get redone as wel when the timezone changes? Maybe someone updated the timezone between making the two employees then?
Just got message from the site owners that they have coupled their Outlook Calendar to their employees and all are linked up there. Also the setting "Remove outlook calander busy slots" is enabled; yet the issue still persist oddly. I assume the coupling works regardless if the service is created before the coupling of the calendar?
I have found an example regarding a service with name: "Wie ben ik? (Onthaalklas en 1ste Kleuterklas)". Which you can find on page: https://neerhof-vzw.be/onze-activiteiten/voor-scholen/ I can book a session on the 28 of November 2024 from 14:00 till 15:00 even though that slot is already taken in the calendar.
I got the feeling we are missing something basic as to why this does not work.
We seem to have an odd issue of double booking regarding services with two employees who have alternating holidays.
Employee settings
employee1: holidays
employee2: holidays
Both employees are available only on Tuesdays and Thursdays from 10:00 til 15:00.
Issue:
When trying to book service X, on 10/12/'24, I see a valid slot for 14:00-15:00 even though this slot is already taken by service Y from 10:00-15:00
Double booking should not be possible in this case? employee1 is on holiday then, employee2 is free.
Yet when booking service X for that slot employee2 is selected for both.
Any idea why?
Any config rules we can check for this?
The issue is as far as we know only occurs on events regarding those two employees.
Attached files: Bijlage 1.png
Bijlage 2.png
Hello,
Thank you for reaching out to us.
Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties.
You can write credentials here just check PRIVATE Reply so nobody can see them except us.
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hello,
Thank you for the update on this.
This is most likely a time zone issue on your website.
Amelia doesn't have any time zone settings, and it relies on WordPress' General settings. Here's how it works:
All times in the back-end of Amelia will be shown exactly how you save them, so (for example) if your employee works from 09:00 - 17:00, or if there's an appointment from 09:00 - 10:00, that's how you will see them in the back-end.
If you enable "Show booking slots in client time zone" in Amelia's General settings, though, that may not be what your customers see, depending on where they're located, and what your WordPress site has been configured.
If this option in Amelia's General settings is disabled, all times on the front end will be the same as times in the back end. So, if your employee's work hours are from 09:00 - 17:00 in UTC+1, with this option disabled, regardless if your customer is in UTC+1, or in UTC+10 - they will still see times from 09:00 - 17:00, so if you have customers in multiple time zones, it's advisable to enable this option in Amelia's General Settings.
Important: In order for Amelia to store correct appointment times in the database (which is almost always in UTC time zone), you need to edit the WordPress time zone to show the city you're in (or the city in your time zone), like this:
This way, when Daylight Savings Time starts (or ends), the times will be adjusted accordingly and you won't have to worry about them anymore.
If you save your Time Zone in UTC+/- format, you may experience issues with Daylight Savings Time:
Explanation: When you configure the time zone to be "UTC+1" it will always be UTC+1. So, if we take Belgrade, Serbia as an example - without Daylight Savings Time, it is in UTC+1 time zone, but when Daylight Savings Time starts, Belgrade is in UTC+2. If you leave the time zone to be hard-coded to UTC+1, the times that your customers book on the front end will not be properly adjusted to what you see in the back end.
Example with UTC+1 configured: It is mid-summer, and Belgrade is in UTC+2. "Show booking slots in client time zone" is enabled, and a customer from Belgrade opens your website to book an appointment. The working hours of your employee are set from 09:00 - 17:00 (in UTC+1), but the customer sees them as 10:00 - 18:00. This is because the time zone is hard-coded in the back-end, while on the front-end it shows the time in UTC+2. So, a customer books an appointment for 10:00, and shows up at 10:00, while you expect to see them at 09:00.
Please note: If you hard-coded the time zone, and you have booked appointments, once you switch the time zone in WordPress to your city, it will adjust the times in Amelia's appointments to fit the time zone your city is currently in. This happens because (as mentioned above) the times are saved in UTC in the database, and it's adjusted in the plugin programmatically. So, if you have a hard-coded time zone set to UTC+1, and someone booked an appointment for 09:00, that time is saved as 08:00 in the database. When you change the time zone to your city (which is now in UTC+2), the appointment time will be adjusted to the time saved in the database 08:00 + 2:00, so the appointment time will switch to 10:00. The only solution, in this case, is to manually modify the appointment times, but it's the only way to make sure your time zone is properly configured, and that the future appointments will be saved and displayed correctly both for you and your customers on the front-end.
Summary: When you select the city you're in, in WordPress' General Settings, the system automatically calculates the Daylight Savings Time, and shifts the clock accordingly, so if you have any issues with what you see on the front end vs what you see in the back-end, always check the Time Zone in WordPress
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Uroš
Sorry for the delay, missed your reply there;
A time zone issue, that is difficult to see; good tip.
I have checked the General Settings; the Timezone is set to a city (Brussels) so, not an issue there. I have also checked using the frontend while in the same timezone; so the backend and the front-end should be in sync? Given the times shown on the front-end is server time due to the setting "Show booking slots in client time zone" being turned off.
Do employee holiday hours get redone as wel when the timezone changes?
Maybe someone updated the timezone between making the two employees then?
Kind regards
Hi Uroš
Just got message from the site owners that they have coupled their Outlook Calendar to their employees and all are linked up there. Also the setting "Remove outlook calander busy slots" is enabled; yet the issue still persist oddly. I assume the coupling works regardless if the service is created before the coupling of the calendar?
I have found an example regarding a service with name: "Wie ben ik? (Onthaalklas en 1ste Kleuterklas)". Which you can find on page: https://neerhof-vzw.be/onze-activiteiten/voor-scholen/
I can book a session on the 28 of November 2024 from 14:00 till 15:00 even though that slot is already taken in the calendar.
I got the feeling we are missing something basic as to why this does not work.
Any solutions are welcome.
Hello,
Thank you for the update on this.
This could be the issue with the difference in the time zone between the calendar that is connected to an employee and the employee.
Please can you check that and let me now if that is the case.
Looking forward to your reply.
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Uroš
We have forwarded the question to the calendar owners; we will reply back soon hopefully.
Kind regards
Hello,
Glad to hear that.
I am looking forward to your reply.
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi again
We got confirmation that the time zone for the calendar is set to Europe/Brussel
as is the website.
Kind regards
Hello,
We have noted this issue and it will be resolved in the next Amelia update.
Please let me know if you have any other questions.
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Uroš
Thank you for the confirmation; looking forward to it.
Kind regards
Hello,
Glad to be able to assist you.
Please let me know if you have any other questions.
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables