Problem: The client is experiencing issues with translating content after mapping it to English GB while using a custom language with the language code en-gb. Adding glossary terms also fails. They are further concerned about how the URL will display for different language versions and whether the system will change the URL when duplicating content for English UK.
Solution: 1. The English mapping option can only be used once and is already utilized for the site's default language. We recommend duplicating the original English content to English UK and English AU.
2. WPML will automatically handle the URL display for different language versions. Each language has a code in WPML > Languages > Edit languages, which will be used in the URL format. For example, if the site is set to "Directories per language" and you create a custom language using the code "en-gb", then English UK will be available at http://www.sitename.com/en/.
3. If you create a duplicate for English UK, you will find it at: https://www.sitename.com/en-gb/yourpage. The original site URL and other URLs will remain unchanged.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing 404 errors on their website due to URLs that appear to be incorrectly encoded or truncated. This issue is particularly occurring with URLs containing non-Latin characters, such as Cyrillic for the Russian language. Solution: 1. We recommend enabling URL Encoding for languages with non-Latin characters to ensure that URLs are processed correctly. To do this: - Navigate to "WPML > Languages" in your WordPress admin dashboard. - Click on "Edit Language". - Find the "Encode URLs" option and select "Yes" for the Russian language. - Save the changes. 2. If a specific URL is still showing a 404 error, check if there is an extra character like
%B
at the end of the URL. Removing this character should resolve the issue. 3. For URLs that are still problematic, use a URL decoder tool like https://www.urldecoder.org/ to check for any incorrect characters. Remove any incorrect characters found.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 problems persist, please open a new support ticket.
Problem: You want to add American and Australian English to your site and are unsure how to handle translations for specific terms like changing 'Campervan Hire' to 'RV Rental' for American English.
Solution: To add custom languages like American and Australian English, navigate to WPML → Languages in your dashboard. Here, you can define the language code and default locale for each variant. You can choose to map a variant to its base or appropriate language for automatic translations, or leave it unmapped for manual translations. We recommend checking the following guides to help you set up:
Additionally, use WPML's Glossary feature to define how specific terms should be translated. This allows you to specify translations like changing 'Campervan Hire' to 'RV Rental'. For more details, visit How to Create and Manage Glossary Entries.
If this solution does not apply to your case, or if it 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 you still need assistance, please open a new support ticket at WPML Support Forum.
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.
