when I make an appointment I get an email telling me I have made a successful appointment with the date and location of the appointment (screenshot_1). So far so good. The issue is when I cancel my appointment. Then I get an email telling me that I have canceled my appointment for a date of the appointment which is not correct as you can see in screenshot_2. It shows a date which is exactly two days earlier than the original appointment date.
I'm using %appointment_date_time% placeholder for both Appointment Approved and Appointment Cancelled notifications.
I dug around to see where the problem is and found out that when you set the Minimum time required before canceling setting for a specific period (in my case 2 days) it takes this period and subtracts it from the appointment original date and then uses it as appointment date in the Appointment Cancelled notification.
I tried this with other values as well and I can reproduce this issue every time. It only sends the correct date when this setting (Minimum time required before canceling) is disabled.
I have disabled it for now because I do not want to send incorrect notifications to our customers but this solution is not good enough for us because now our customers can cancel an appointment 5 minutes before it starts and we are trying to avoid such cases.
Please provide me a temporary WP-admin login 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 party. You can write credentials here just check Private Reply so nobody can see them except us.
The timezone is OK and is not the problem. As I said before (also visible in the screenshots), we're talking about days here, not just hours and the difference is always exactly the same as the value of Minimum time required before canceling setting.
I have exactly the same issue on my side. My domain is www.jouwplanner.nl, which is the primary domain in a multisite network. I also tested the issue with different values for Minimum time required before canceling. And I can reproduce it exactly as ihris7ov said.
Please also see my private ticket #2020888 which I added today.
This cannot be coincidence I would think. By the way, timezone is also checked on my side. Nothing going on there.
In my case, there was exactly 24 hour difference between date listed in Cancellation notification and the real date of appointment, which is actually the same amount of time as the 'Minimum time required before cancelling' has set. I also use %appointment_date_time% placeholder.
Hi guys,
I'm using version 1.4.4.
I have the following issue:
when I make an appointment I get an email telling me I have made a successful appointment with the date and location of the appointment (screenshot_1). So far so good. The issue is when I cancel my appointment. Then I get an email telling me that I have canceled my appointment for a date of the appointment which is not correct as you can see in screenshot_2. It shows a date which is exactly two days earlier than the original appointment date.
I'm using %appointment_date_time% placeholder for both Appointment Approved and Appointment Cancelled notifications.
I dug around to see where the problem is and found out that when you set the Minimum time required before canceling setting for a specific period (in my case 2 days) it takes this period and subtracts it from the appointment original date and then uses it as appointment date in the Appointment Cancelled notification.
I tried this with other values as well and I can reproduce this issue every time. It only sends the correct date when this setting (Minimum time required before canceling) is disabled.
I have disabled it for now because I do not want to send incorrect notifications to our customers but this solution is not good enough for us because now our customers can cancel an appointment 5 minutes before it starts and we are trying to avoid such cases.
BR
Hi ihris7ov,
Thank you for your purchase.
Please provide me a temporary WP-admin login 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 party. You can write credentials here just check Private Reply so nobody can see them except us.
Best regards.
Kind Regards,
Miloš Jovanović
[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 ihris7ov,
I just tested out on my local machine and also on our server but we were not able to reproduce the issue.
So the best case for this would be if we can take a look at your site to see what may be the issue.
Also please check if the timezone in WordPress dashboard is correct with the time zone that you are in.
Best regards.
Kind Regards,
Miloš Jovanović
[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,
The timezone is OK and is not the problem. As I said before (also visible in the screenshots), we're talking about days here, not just hours and the difference is always exactly the same as the value of Minimum time required before canceling setting.
Also, did you test it with version 1.4.4?
BR
Hi ihris7ov,
Exactly the same use case and settings like you described me below and with the latest 1.4.4 version of the plugin.
But we can not reproduce it, which is very strange that this is happening on your side.
If this is a bug or something else it will be reproduced on our side as well.
Best regards.
Kind Regards,
Miloš Jovanović
[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 guys,
I have exactly the same issue on my side. My domain is www.jouwplanner.nl, which is the primary domain in a multisite network. I also tested the issue with different values for Minimum time required before canceling. And I can reproduce it exactly as ihris7ov said.
Please also see my private ticket #2020888 which I added today.
This cannot be coincidence I would think. By the way, timezone is also checked on my side. Nothing going on there.
Hello,
I have the same issue with version 5.2.1.
problems placeholders:
%appointment_cancel_url%
%appointment_start_time%
%appointment_date_time%
%service_name%
Hello,
the same here.
Amelia version 1.5.1, WP version 5.2.1.
In my case, there was exactly 24 hour difference between date listed in Cancellation notification and the real date of appointment, which is actually the same amount of time as the 'Minimum time required before cancelling' has set. I also use %appointment_date_time% placeholder.
Hi guys,
I've just updated to the latest version 2.0 and this issue is resolved. I've tested it and everything is working fine.
BR