Problem: You are using WPML to translate your WordPress site with WooCommerce and are trying to translate the PayPal button text 'Paga in 3 rate' into English (coming via 'WooCommerce PayPal Payments' plugin). However, you couldn't find where to translate the PayPal button string in WPML’s String Translation section or WooCommerce settings.
Solution: First, ensure that your WPML plugin and all related add-ons are updated to the latest version. Follow these steps to attempt locating and translating the string: 1. Navigate to WPML → String Translation. 2. Enable the option to auto-register strings. 3. Visit the page displaying the untranslated strings. 4. Return to WPML → String Translation to check if the string has been registered. 5. If found, proceed to translate the registered string. For more detailed instructions, visit finding strings that don't appear on the String Translation page. If the string is not available, it might be due to it being sourced from an external iframe, as in the case of the PayPal button. This content is not directly translatable through WPML because it either does not pass the language parameter correctly or PayPal applies its own localization logic. In such cases, consult with the 'WooCommerce PayPal Payments' support.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: You are trying to translate products in your e-commerce store using WPML, but the translated product variants are not selectable, making the products unpurchasable. Solution: 1) Ensure you are using WooCommerce Multilingual and have translated the attributes to the second language from WooCommerce Multilingual > Attributes. More information can be found here: https://wpml.org/documentation/related-projects/woocommerce-multilingual/ 2) At the bottom of the page from WooCommerce Multilingual > Attributes, click the button that synchronizes variations across products. 3) If you are using local attributes, switch to using global attributes. Add global terms to your global furniture attribute and translate them to the second language from the WCML attribute tab. Then, edit your default language product, remove current attributes and variations, and add existing global attributes. Create variations from these and save the product. Translate, and it should work fine.
If this solution does not resolve your issue or seems outdated, we recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is unable to translate WooCommerce Checkout Manager by quadlayers using WPML. Solution: If you're experiencing this issue, we recommend trying the following steps: 1. Navigate to WPML → String Translation. Scroll to the bottom of the page and click on the Translate texts in admin screens link. This will direct you to a searchable list of admin strings. Search for your specific string, select it, and then click Add to String Translation. 2. Alternatively, you can make a small change to the field title or content and save it. Then, go to WPML > String Translation > Translate texts in admin screen, search for the adjusted string, and add it to String Translation. Finally, translate the string using the WPML String Translation. For more detailed guidance, refer to our documentation on translating admin and settings strings.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket.
