almhdy

Understood. I confirm that I will not ask any WordPress.org forum user for site access anywhere, on or off the forums, under any circumstance. I understand this policy fully and will follow it strictly.

Thank you for the clarification.

I understand the forum policy and I confirm that I will not request or accept login, admin, or server access from users on the WordPress.org forums.

Going forward, I’ll provide support publicly here using the recommended debugging and troubleshooting methods, and will direct paying customers to my official support channels when applicable.

I appreciate the explanation and will follow these guidelines strictly.

At this time, we won’t be able to add official support for AVADA/Fusion Builder to our plugin. The AVADA theme adds significant layers of HTML code to the page content. When processed by an AI model, this drastically increases the response time (often causing AJAX timeout errors) and consumes a very high number of input/output tokens, which makes it cost-prohibitive for most users.

Therefore, rather than investing in an unstable and expensive integration, we’re directing our development toward solutions that work reliably across most themes.

In the meantime, we’ve found that Google Translate or DeepL Pro work much better with AVADA and would recommend those for your translation needs.

Fixed: Download version 2.1.0, and check the box of the this feature on settings page.

• This reply was modified 5 months, 3 weeks ago by almhdy.

Fixed, download the new version 2.0.3

Thank you for your question. Currently, our plugin does not automatically Sync internal links, which is why you’re seeing them point to the default language pages.

I’ve added this feature to our development roadmap for a future update.

For now, you would need to manually update those links in the Elementor editor for each translation. We apologize for the inconvenience.

The plugin is not compatible with elementor. but we work on that, the next release will be work with elementor.