Problem: If you're experiencing issues where the translated content of your custom post types is displayed using the default single post template instead of your custom template, this might be due to the templates not being translated. Solution: We recommend translating your Site Templates and Template Parts to ensure they apply correctly in different languages. First, check if these templates are available for translation at WPML > Translation Management > Dashboard. If they are not translated, create a translation job for each template or template part. You can then access and complete these translations to 100% using the WPML Translation Editor or automatic translation at WPML > Translations. Additionally, be aware of potential display condition issues when editing templates in a second language within the Site Editor. A workaround for this issue can be found at https://wpml.org/errata/template-is-not-applied-to-translated-page/.
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 at WPML support forum.
Problem: The client is using the GreenShift Builder with WPML to build and translate their website. While translating the homepage using WPML’s Advanced Translation Editor, the translated version displays the default language content instead of the translated content. Additionally, an error in the backend indicates that the block contains unexpected or invalid content, prompting a block recovery message. Solution: We resolved the issue by updating the GreenShift plugin and its add-ons to the latest version. It is crucial to follow the correct WPML translation process and avoid editing the translated content directly in the Gutenberg editor. After these updates and following the proper procedures, we tested the system thoroughly and confirmed that everything is now working as expected.
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. If the problem persists, please open a new support ticket.
Problem: The client is developing a site and wants to set up the primary .com domain in American English with a directory for British English. Solution: 1. Go to WPML > Languages > Site Languages and click "Edit Languages". 2. Add a new custom language using the language code "en-us" for American English. By default, the pre-installed English in WPML uses the locale en_US. Change this to en_GB for British English. 3. You can upload custom flags for each language. Find flags ready to use in WPML's plugin folder on the server. For more details on custom flags, visit Guide for flags. 4. In WPML > Languages > Language URL format, select "Different languages in directories" and save the WordPress Permalinks if you adjust this option. 5. Ensure that American English is set as the Site Default language in WPML > Languages > Site Languages.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
