Problem: The client wants to prevent the translation of the company name 'Routes' to 'Rutas' in different languages on their website. Solution: If you're experiencing this issue, we recommend you add the string 'Routes' to the glossary to prevent its translation. You can follow the steps described in our guide on how to create and manage glossary entries. Here is the link to the guide: How to Create and Manage Glossary Entries.
Please note that this solution might be irrelevant if it's outdated or not applicable to your 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 for further assistance.
Problem: You have a blog section but cannot see options to translate these pages. Solution: We recommend activating the translation options for your 'Pages', 'Posts', and other Custom Post Types (CPTs). You can do this by following the instructions provided in our documentation on Translating Custom Posts. Once activated, this will enable the '+' icon on the CPT to translate content and add the language interfaces. Additionally, you will be able to translate via WPML -> Translation Management.
If this solution does not apply to your case, or if it seems outdated, please check our related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if you need further assistance. You can do so at WPML support forum.
Problem: The client was experiencing issues with automatic translation credits and needed assistance in setting up American English as a new language on their site.
Solution: 1. If the client recently changed the domain, domain provider, or server, they need to re-register WPML: - Go to https://wpml.org/account/websites/ - Delete the site URL if it's already registered. - Re-enter the site URL to create a new site key. - Copy the key and register WPML again under Plugins > Install > Commercial.
2. To set up American English as a new language: - Go to Languages > Site languages > Edit languages. - Edit the default English language to change the "default locale" to en_GB. - Add a new language and create a custom language for US English, using en_US as the "default locale".
3. If encountering issues with JS scripts and CSS sheets being blocked, consider disabling the rules or the plugin "CSS JS Manager, Async JavaScript, Defer Render Blocking CSS".
4. Regarding translation credits, once the client reaches a certain usage, they will be prompted to pay the open amount as an internal fraud security measure.
If the solution provided here is outdated or not applicable to your case, we recommend opening a new support ticket. We also 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 contact us at the WPML support forum.
Problem: The client was unable to locate the string "Manage booking" for translation in their theme named "Renta Camper Van". The PHP code provided by the developer was suspected to be incorrect, as it used the wrong text domain and incorrect quotation marks.
Solution: We advised the client to ensure that the correct text domain is used in the PHP code. The correct code should look like this:
We recommended following the steps in our article on translating the theme you created, which includes rescanning the theme for strings.
Additionally, we suggested enabling the option "Look for strings while pages are rendered" by: 1. Going to WPML → String Translation. 2. Enabling the option "Look for strings while pages are rendered". 3. Navigating to the page where the untranslated strings are displayed. 4. Returning to WPML → String Translation to check if the string has been registered. 5. Translating the string if it has been found.
If the solution provided here is outdated or not applicable to your case, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
Problem: The client needed to translate the 'Book Now' text located in the banner area of the template on their website. Solution: We recommended that the client use the WPML String Translation plugin to translate the strings. Detailed instructions on how to use the plugin can be found here: https://wpml.org/documentation/getting-started-guide/string-translation/ Additionally, we asked the client to provide information on where the 'top banner' section is generated, as it was not clear whether it was part of theme options, a page builder, or hard-coded into the template.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we encourage you to open a new support ticket. We also 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 contact us in the WPML support forum.
Problem: The client needed to translate form field labels such as 'Country', 'pickup location', and 'dropoff location' that were not translated on a multilingual website.
Solution: 1) We instructed the client to scan the theme for translatable strings by navigating to WPML > Theme and Plugins Localization.
2) After scanning, the client should go to WPML > String Translation and search for the label they want to translate.
3) Once the label appears in the search results, the client can add a translation by clicking on the '+' icon below the flag of the language they are translating to.
4) Finally, the client should clear the WP Rocket cache to see the changes on the front end.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we recommend opening a new support ticket. We also highly suggest 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 contact us through the WPML support forum.
