Problem: The client added text that was not appearing for translation in WPML. Solution: First, we recommend wrapping the string with the gettext function to make it translatable. For example, use the following code:
Next, follow these steps to ensure the string appears in WPML's String Translation: 1. Go to String Translation. 2. Enable the "Auto-register strings" option. 3. Visit the page on the front end where the string is displayed. 4. Disable the "Auto-register strings" option. 5. Search for the string to translate it. For detailed instructions, please visit our guide on finding strings that don't appear on the String Translation page.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket.
Problem: The client added two fields with WooCommerce Custom Fields to the products in their shop and translated them via String Translation. However, after changing the button text to 'Add to Cart' and translating it, the new text did not appear on the front end. Solution: We recommend ensuring that the Custom Fields are set as translatable in WPML Settings. Follow these steps: 1. Visit the documentation on Translating Custom Fields and verify that the fields are translatable. 2. Navigate to WordPress Dashboard > WPML > String Translation and enable the Auto Register feature at the bottom of the page. 3. Refresh the front end of the page. 4. Return to String Translation and reload the page to check for new instances of the 'Add to Cart' text. For additional information, refer to the documentation on finding strings that don't appear on the String Translation page.
If this solution does not seem relevant to your issue, please open a new support ticket by visiting the WPML support forum.
