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!

Okay
  Public Ticket #1684150
RangeError: invalid language tag: lt_LT
Closed

Comments

  •  2
    kiprasbiel started the conversation

    Hello, I get this error ( RangeError: invalid language tag: lt_LT ) in the console while trying to access a page with Amelia widgets on it. And Amelia widgets are not visible when error is present. 

  • [deleted] replied

    Hi kiprasbiel,
    Thank you for the 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.

  •   kiprasbiel replied privately
  • [deleted] replied

    Hi kiprasbiel,

    It is fixed and it should work now. We will add this fix in the next update.

  •  2
    kiprasbiel replied

    Well done! Works fine!

  • [deleted] replied

    Hi kiprasbiel,

    You are welcome. We'd greatly appreciate it if you could take a minute and leave a review on CodeCanyon on this link. Thanks!