When you attempt to create a new appointment from admin, no matter which employee or service is selected, the time slots are every 5 minutes instead of selected time for the service itself.
Can you please check in the Amelia Settings-> General settings which step is chosen in the Default Time Slot Step: ( attachment) I assume that for you is set to be 5 minutes.
You are assuming right, Default Time Slot Step is set to 5 minutes, but before the latest update it was working as expected. I mean, when you are creating a new appointment from admin, the time slots interval should be the one configured as per service.
Could you please enable the option "Use service duration for booking a time slot " in Amelia -> Settings -> General Settings and let me know if this solves your issue?
If you have any further questions or concerns feel free to ask,
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.
You have services with duration of 10, 15, 20 and 30 minutes and you enabled the option in the settings page Use service duration for booking a time slot.
So now for the each employee, based on which service they provide the time slots will be used , from their start working time, and then using the duration of the services.
The default time slot step is not used when the Use service duration for booking a time slot option is enabled.
Use service duration for booking a time slot: Enable this option if you want to make time slot step the same as service duration in the booking process.
So when this option is enabled the time slot step should be the one defined in the service.
In fact, if this option is disabled, the time slot steps in frontend form are every 5 minutes (default time), but when it's enabled, the frontend form shows the time slot steps as specified in the service (10, 15, 20 or 30 minutes) which is perfect.
The same should happens (but it's not) when you try to create an appointment from admin interface. It shows time slot steps every 5 minutes no matter what service configuration is.
I insist that this was working fine on previous versions and suddenly stopped working on last update.
Any updates regarding this issue? My customer's secretary is complaining about this issue since she usually creates appointments from admin area for old aged patients.
Good news: this bug is now fixed with the latest update.
Bad news: now there is a new issue. If an appointment is canceled or rejected, it's still not available for selection until it's completely deleted. I mean, the only way to create a new appointment for a canceled time slot is by deleting it before creating a new one.
Please note that this only happens in the backend. The frontend is working fine.
Glad to hear the bug is fixed! As for the other issue, that is how Amelia works, you can can edit existing appointment or delete it before you want to make new one for the same time slot.
Actually it doesn't look fine for me. Shouldn't work in a similar way in both back and front ends?
Let's assume, as in my customer's case, that a patient creates an appointment for the first time slot next Monday but a few days before he decides to cancel it. Why anybody else shouldn't be allowed to pick that canceled slot?
In fact, it works as expected in the frontend form which is perfect, but in backend form, it's not possible to take that appointment slot until the canceled/rejected slot is DELETED.
I'm seeing an inconsistency here, both ways (front and backends) are acting in different ways.
This is how it works from the beginning, to prevent mistakes. Now you can add customer on Edit button, but we will consider your use case and try to find the best solution for this problem.
When you attempt to create a new appointment from admin, no matter which employee or service is selected, the time slots are every 5 minutes instead of selected time for the service itself.
Updated to latest version: 2.3
Please see attached png
HI bobygoma,
Can you please check in the Amelia Settings-> General settings which step is chosen in the Default Time Slot Step: ( attachment)
I assume that for you is set to be 5 minutes.
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 Bogdan,
You are assuming right, Default Time Slot Step is set to 5 minutes, but before the latest update it was working as expected.
I mean, when you are creating a new appointment from admin, the time slots interval should be the one configured as per service.
Hello bobygoma,
Could you please enable the option "Use service duration for booking a time slot " in Amelia -> Settings -> General Settings and let me know if this solves your issue?
If you have any further questions or concerns feel free to ask,
Hi Marija,
The option is already enabled. I've disabled/enabled and saved just in case but no luck.
As a friendly reminder, this was working as expected in previous plugin version.
Hi bobygoma,
Can you please tell me the duration of some services so I can try to recreate the same problem on our side.
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 Bodgan,
We have many services using 15, 20 and 30 minutes as duration. Because of these durations, we had to set the default time to 5 minutes.
Please let me know if you need a temporally access to check it in our production site.
Regards
Hi bobygoma,
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 bobygoma,
As I can see everything seems fine.
You have services with duration of 10, 15, 20 and 30 minutes and you enabled the option in the settings page Use service duration for booking a time slot.
So now for the each employee, based on which service they provide the time slots will be used , from their start working time, and then using the duration of the services.
The default time slot step is not used when the Use service duration for booking a time slot option is enabled.
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 Bodgan,
Sorry but I think you are wrong.
Use service duration for booking a time slot: Enable this option if you want to make time slot step the same as service duration in the booking process.
So when this option is enabled the time slot step should be the one defined in the service.
In fact, if this option is disabled, the time slot steps in frontend form are every 5 minutes (default time), but when it's enabled, the frontend form shows the time slot steps as specified in the service (10, 15, 20 or 30 minutes) which is perfect.
The same should happens (but it's not) when you try to create an appointment from admin interface. It shows time slot steps every 5 minutes no matter what service configuration is.
I insist that this was working fine on previous versions and suddenly stopped working on last update.
Hi bobygoma,
Ok thank you for your feedback and explanation.
So the issue is in the backend with the latest version.
I forwarded this to my team so we can test this out.
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 Bogdan,
Any updates regarding this issue? My customer's secretary is complaining about this issue since she usually creates appointments from admin area for old aged patients.
Thanks in advance,
Regards.
Hi bobygoma,
The issue is forwarded, and I am waiting for the fix.
In the meantime , as you said, this was working on the older versions of the plugin.
I can send you any old version of our plugin if you like, until the fix is included in the update.
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 Bodgan,
Good news: this bug is now fixed with the latest update.
Bad news: now there is a new issue. If an appointment is canceled or rejected, it's still not available for selection until it's completely deleted.
I mean, the only way to create a new appointment for a canceled time slot is by deleting it before creating a new one.
Please note that this only happens in the backend. The frontend is working fine.
Hi bobygoma,
Bogdan is out of the office today.
Glad to hear the bug is fixed! As for the other issue, that is how Amelia works, you can can edit existing appointment or delete it before you want to make new one for the same time slot.
Hope that is not a problem.
Hi Nevena!
Actually it doesn't look fine for me. Shouldn't work in a similar way in both back and front ends?
Let's assume, as in my customer's case, that a patient creates an appointment for the first time slot next Monday but a few days before he decides to cancel it. Why anybody else shouldn't be allowed to pick that canceled slot?
In fact, it works as expected in the frontend form which is perfect, but in backend form, it's not possible to take that appointment slot until the canceled/rejected slot is DELETED.
I'm seeing an inconsistency here, both ways (front and backends) are acting in different ways.
Make sense?
Hi bobygoma,
This is how it works from the beginning, to prevent mistakes. Now you can add customer on Edit button, but we will consider your use case and try to find the best solution for this problem.