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 just purchased and installed the plugin. When I open any page of the plugin it is showing blank. I am getting this error in the console.
Uncaught TypeError: Cannot set property $http of #<wn> which has only a getter
at Object.<anonymous> (amelia-booking.js?ver=4.2:1)
at r (amelia-booking.js?ver=4.2:1)
at Object.<anonymous> (amelia-booking.js?ver=4.2:1)
at r (amelia-booking.js?ver=4.2:1)
at amelia-booking.js?ver=4.2:1
at amelia-booking.js?ver=4.2:1
Hi Sumit,
thank you for your purchase!
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.
Hi Sumit!
Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.
It was a conflict with LMS plugin; our team has fixed it now trough the database.
If you have any further questions or issues, please feel free to open a new ticket, and we'll gladly help.