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!
I have created a category, service and employee and connected all 3 together and yet it wont allow me to place it on a page keep getting this "Notice: Please create category, service and employee first". Never had this problem on ver 2.0 but since I installed ver 2.1 I haven't been able to make it work. I have tried uninstalling and re installing the pugin and nothing.
Hello Arvinder Singh,
Thank you for your purchase!
Apologies for replying late, we are not working on weekends.
Unfortunately, we encountered some issue/bug after the last update with Gutenberg blocks and this is the cause of the error that you get (it comes up when no events (no tags for events) are created in Amelia).
Sorry for any inconvenience this have caused. We will fix this in our next update.
Until then, please find the following file in your WordPress folder:
../wp-content/plugins/ameliabooking/src/Infrastructure/Repository/Booking/Event/EventTagsRepository.php
and in line 130 replace this:
with this:
Also, the issue won't be there if you use Classic editor.
Again, sorry for any inconveniences.
If you have any further questions or concerns don't hesitate to ask,