Andrei

Hey there,

Thanks for reaching out to us!

The TranslatePress trp-ajax.php file might be blocked by a security plugin such as WordFence or host configuration. Try to disable such security plugins or ask your host about this issue.

It’s also possible that your host server configuration doesn’t allow TranslatePress to perform a direct database connection. In this case, install this plugin to switch to a WordPress native approach. The only drawback is that on some large websites it can be a bit slower to translate front-end dynamic texts. https://translatepress.com/download/1151690/

The issue can also be caused by a repeated detection of the same front-end string displayed using JavaScript. In this case you should notice numerous trp-ajax.php calls (20+) in the browser console under Network tab. To solve this, identify the html node that contains that overdetected text and use TP Advanced Settings option Exclude from dynamic translation to input the JS/CSS selector for that node.
Another approach to the same issue would be to install this plugin which reduces the number of allowed detection of the same dynamic string to a lower number: https://translatepress.com/download/1151694/

Hello there,

Thanks for letting us know about this!

I tried looking into this but on our own instances and it seems to be working as intended.

Would you mind going into further detail about this? So if I understand correctly your URL’s are getting translated but inconsistently. Would you mind sharing an example?

Looking forward to your reply.

Hey there,

I tried looking at this on your website but it seems your issue has been solved.

Please do not hesitate to write back to us if you encounter any other problems.

Hey there,

Thanks for reaching out

The translations made with TranslatePress are string-based, so those are saved string by string in your database. In other words, the architecture of these plugins is different, TP saves translations at the string level, while Polylang saves at the post level, making the translations to be incompatible.

If you decide to use our plugin, you will need to translate the content from 0.

/**
 * Deactivate WP Bakery integration with TranslatePress
 */
add_action ('init', 'trpc_deactivate_wp_bakery_conditional_display_by_language');
function trpc_deactivate_wp_bakery_conditional_display_by_language(){
    $trp_wpbakery = TRP_WPBakery::instance();
    remove_action('init', [$trp_wpbakery, 'init'], PHP_INT_MAX);
}

We couldn’t replicate your issue with the latest versions of both plugins. My guess is that you have a WP Bakery element added by plugin other than the default WPBakery or you have a default one that’s configured differently than I could replicate.

Either case, it conflicts with TranslatePress’s code that adds language conditional section for that element. It’s unclear from the error what is the name of the conflicting element. As a workaround, try placing above code in a new plugin. It removes the language conditional section but keeps the rest of functionality for both plugins. If you need language conditional, you can try other methods such as the conditional shortcode.

Hey there,

Thanks for reaching out to us!

At the moment our team is aware of this existing problem and they are doing their best to get it sorted out as soon as possible.

Until this is fixed we have a workaround, go to Advanced TP Settings -> Exclude Gettext Strings and add the woocommerce-paypal-payments to domain and make sure to save afterwards.

Hey there,

Thanks for reaching out to us!

Apologies for not getting back to you any sooner!

At the moment our development team is checking the problem that you are experiencing and we will get back to you as soon as possible.

Thank you for your patience so far!