We're Moving to a New Support Platform – Starting June 1st!
We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.
You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.
While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.
We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.
Thanks for your continued support and trust – we’re excited to bring you an even better support experience!
This is actually a bug report, since my support licence expired this is the only way to report it.
Lets suppose that 2 users opened the appointment form from different locations.
Both user have been selected the same time slot for the same service. One of them confirms the appointment but the other one kept the form opened for a while.
Now the 2nd user confirms the appointment which shouldn't be available anymore.
What happens? Now both users have an appointment at the same time in same service.
This is not a mis-configuration related issue because by refreshing the page, the appointment took by the first user is not available anymore.
Apparently there are no validation at the backend, only in frontend. The submit process should look into the DB if the appointment was already taken before inserting it.
Please fix this ASAP! Customers are complaining about this!
Hi Bobygoma,
Thank you for your inquiry.
Can you please tell us the version of our plugin that you are using? And also, which payment method you are using? We've had this bug in one of the previous versions but we have fixed it and release a fix in version 2.1.
Best regards.