Back to Community
Home / Community / Plugin → Translate multilingual sites – translatepress

Troubleshooting TranslatePress: Fixing Checkout and Payment Issues in Secondary Languages

25 threads Sep 11, 2025 Plugin → Translate multilingual sites – translatepress

Content

Many WordPress users rely on 'Translate Multilingual sites – TranslatePress' to create multilingual stores. However, a common and frustrating issue arises when the checkout page or payment gateways malfunction in a secondary language, while working perfectly in the default language. This guide will help you understand why this happens and walk you through the most effective solutions.

Understanding the Problem

These issues typically stem from conflicts between TranslatePress and other plugins, particularly those handling sensitive e-commerce functions like payment gateways (e.g., PayPal, Mollie) or checkout fields. When a page is translated, TranslatePress can sometimes modify or interfere with dynamic JavaScript elements or specific strings that these plugins rely on to function correctly. This can result in problems like:

  • Payment buttons not loading or becoming unclickable.
  • Payment methods not appearing in the language-switched checkout.
  • Checkout formatting breaking in specific languages.
  • Critical form data, like payment gateway information, not being passed correctly.

Common Solutions to Try

1. Clear All Caches

This is always the first step. Caching can serve an old, broken version of your translated page.

  • Clear your browser cache and test in an incognito/private window.
  • Clear any server-side, plugin, or CDN caches (e.g., from WP Rocket, W3 Total Cache, Cloudflare).

2. Exclude Plugin Strings from Translation

Many payment gateway issues are resolved by preventing TranslatePress from translating the specific text domains of other plugins. This allows those plugins to operate in their original state.

  1. Navigate to TranslatePress → Settings → Advanced.
  2. Find the Exclude Gettext Strings option.
  3. Add the text domain of the problematic plugin. Common examples include:
    • woocommerce-paypal-payments (for PayPal)
    • mollie-payments-for-woocommerce (for Mollie)
    • woo-viet (as seen in one thread)
    • woocommerce (for general WooCommerce strings)
  4. Save changes and test your checkout again.

3. Exclude Dynamic Strings from Forms

If a payment form is failing because TranslatePress is adding a language parameter (like trp-form-language) that the gateway doesn't recognize, you can stop this behavior with code. The following code snippet can be added to your child theme's functions.php file or via a code snippets plugin.

/*
 * Do not add trp_form_inputs
 */
add_filter('trp_form_inputs', 'trp_remove_trp_form_language', 10, 4);
function trp_remove_trp_form_language($input, $trp_language, $slug, $row)
{
    return '';
}

Warning: Always back up your site before adding custom code.

4. Check for and Install Plugin Updates

The 'Translate Multilingual sites – TranslatePress' team regularly releases updates that fix known conflicts. In several threads, a specific bug with PayPal in v.2.9.3 was fixed in a subsequent update. Always ensure you are running the latest versions of TranslatePress, WooCommerce, and your payment plugins.

5. Perform a Conflict Test

If the above steps don't work, a more extensive conflict test is needed.

  1. Temporarily switch to a default WordPress theme (like Twenty Twenty-Four).
  2. Deactivate all plugins except for WooCommerce and TranslatePress.
  3. Test if the checkout works in the secondary language. If it does, you have a conflict.
  4. Reactivate your plugins one by one, testing after each activation, to identify the culprit.

Conclusion

Checkout and payment issues in secondary languages are almost always due to plugin conflicts. By methodically working through these solutions—clearing cache, excluding strings, checking for updates, and performing conflict tests—you can usually identify and resolve the problem, providing a smooth checkout experience for all your customers, no matter what language they speak.

Related Support Threads Support