The client reported that after moving their site, the language parameter was not included in the URLs as expected, despite having set the URL to use directories for different languages.
Solution:
We first checked if there was a compatibility issue and requested screenshots of certain dashboard pages to track the issue. It was discovered that the Custom Post Type 'Destinations' was not set to be translated. We advised the client to:
1. Ensure a site backup is done. 2. Go to WPML>>Settings>>Custom Post Types translation and set the 'Destinations' post type to 'Translatable – only show translated items' and save the changes. 3. Visit Settings>>Permalinks and resave the settings to ensure the changes take effect. For more details, refer to our documentation on translating custom posts.
If this solution does not resolve your issue or seems outdated, please 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. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client is setting up a development copy of their site and has installed WPML on the development domain. They are facing issues with WPML not recognizing the site as a development copy and are unsure how to proceed with the license key and the import/export of WPML content. Solution: If you're setting up a development copy of your site and need to manage WPML's license and content, follow these steps: 1. Generate a new site key for the development domain by visiting https://wpml.org/account/sites. You can specify the key as 'Development' during this process. 2. To duplicate your site, consider using the 'Duplicator' plugin. Documentation and a tutorial for Duplicator can be found at https://snapcreek.com/duplicator/docs/ and https://www.youtube.com/watch?v=3YDQ3Ey_2wY. 3. After migration, register WPML on your new site with the new key. 4. For manual content transfer, use the WPML Import/Export plugin. You can download and install it from https://wpml.org/download/wpml-export-and-import/?section=changelog. 5. Manually configure any custom taxonomies or language settings on the development site before importing content.
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 at WPML support forum.
Problem: The client is trying to translate content on their website and wants to avoid being charged again for translating the same section when it appears on different pages, especially when there are slight variations specific to different locations.
Solution: We explained that the WPML's Automatic Translation Engine (ATE) does not charge extra credits for retranslating content that has already been translated, thanks to the Translation Memory feature. However, ATE identifies sentences based on punctuation marks and line breaks. If the sentences are structurally similar but contain different words (like country or city names), they are considered new sentences and require separate translations. We recommended using consistent punctuation to help ATE recognize and reuse translations more effectively.
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: If you're experiencing issues where the call to action button text reverts back to English after saving the page post adding page-level CSS in Spectra Editor, even though it was initially translated correctly. Solution: We recommend following these steps: 1. Open the default language page in Edit mode. 2. Make a small change, such as adding a '+' sign in the page title. 3. Update the page by pressing the “Update” button. 4. Remove the small change made in step 2. 5. Update the page again. 6. Open the translated page in WPML Translation Editor and ensure the translation is 100% complete, then press the complete button. This should maintain the correct translation on the frontend.
If this solution does not resolve your issue, or if it 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are using Thrive Editor with WPML, which is not fully compatible, causing issues with the display of translated pages. You are considering either editing each translated page individually or switching to a compatible editor like Elementor and re-translating the content. Solution: If you choose to switch to a new editor like Elementor and re-save the original pages, WPML will treat this as creating new content due to the different shortcodes and content blocks used by different editors. Consequently, WPML will attempt to re-translate the content, which may incur additional translation costs. If you decide to manually fix the design issues on the translated pages using Thrive Editor, any future updates to the translation might revert these pages to their previous broken state.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum.
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.
