Problem: You are using WPML to translate pages from Dutch to English and have noticed that the translated pages have different content structures, such as varying paragraphs and headlines.
Solution: To support different content structures for translated pages, we recommend using the WordPress Editor. This tool allows you to maintain custom structures for each translation. For detailed guidance on how to manage this, please check the following documentation: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is using WPML for a WordPress site and is concerned about the SEO impact of using /EN/ URL segments for pages that are not translated into English. Solution: We recommend continuing to use the fallback option for untranslated pages. WPML informs Google that these /EN/ pages are displaying the default content temporarily, which prevents them from being seen as duplicate content. This approach will not negatively affect your site's SEO. If you translate these pages later, Google will recognize and index the new content accordingly. For more details, you can check our documentation here: Displaying Untranslated Content on Pages in Secondary Languages.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client is using ACF to store employee information and has pages in both primary and secondary languages. However, in the secondary language, the URL components are not translated and are shown in the primary language. Solution: We recommend the following steps to translate URL components using the WPML plugin: 1. Ensure that the ACF Multilingual plugin is active. 2. Set the translation preference for the Link field to "Translate" by changing the translation mode of the field group to "Expert" and then setting the Link field within the group to "Translate". 3. Open the page/post containing the link field, make a small change in the title, and save the changes. 4. Update the translation. Refer to this guide for details on translating links. 5. For translating specific slugs like 'ons-team' and 'advocaten', ensure that each component (page, custom post type, individual post) is translated correctly. For custom post types, go to "WPML > Settings", locate the post type, set it to "Translatable - Only show translated items", and use the "Set different slugs in different languages" option to specify the slug in the secondary language. More details can be found in this guide.
If these steps do not resolve your 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 further assistance is needed, please open a new support ticket.
Problem: The client is trying to translate three child pages, but after translation, they all incorrectly have 'parent-a' as their parent instead of 'parent-b'. This issue occurs only in the secondary language. Solution: First, ensure you have a backup of your site. Then, we recommend trying the workaround suggested in a related support ticket, which you can find here: WPML support forum post. Additionally, navigate to WPML>>Settings and verify that the 'Posts and pages synchronization' options are enabled, especially the 'Set page parent for translation according to page parent of the original language' option.
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 if the problem persists. You can do so here: WPML support forum.
Problem: The client is experiencing an issue where the page in the secondary language displays an outdated version with old pictures and layout. Solution: We recommend updating the WPML plugin to the latest version (4.6.11) and all related add-ons to ensure you have the latest bug fixes and improvements. You can find the latest versions in your WPML account under My Account -> Downloads. If updates are not visible, click on the 'Check for updates' button in the Plugins → Add New Plugin → Commercial tab. Before updating, make sure to back up your database. After updating, if the issue still persists, try to update the page translation by slightly modifying the original page, saving it, and then navigating to the WPML translation editor to complete the translation.
If this solution does not resolve your issue or seems irrelevant due to being 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 problems continue, please open a new support ticket at WPML support forum for further assistance.
Problem: You need to translate elements like headers and footers created with GeneratePress and Blocks. Solution: We recommend following our detailed guide on how to translate these elements using WPML. You can find the guide here: Translating GeneratePress Theme Using WPML.
If this solution does not apply to your case, or if it seems outdated, please check the 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 if you need further assistance. You can do so at WPML support forum.
Problem: If you're experiencing hreflang errors indicating 'Hreflang to redirect or broken hreflangs' during a site audit, and you notice a URL that contains a mix of primary and secondary language indicators but leads to a page only available in the primary language, this could be due to a translated taxonomy (like a category) being assigned to a post that hasn't been translated into the secondary language. Solution: To resolve this, you have two options: 1. Translate the post associated with the translated taxonomy to ensure consistency and prevent redirection errors. 2. Remove the translation of the category if the post is not meant to be translated. For example, if you remove the translated category 'familierecht' from the post 'Erkenning buitenlandse man van Nederlands kind' and assign it to a non-translated category like 'wpmlxyz', the redirection should not occur. Regarding the use of ChatGPT for translations, currently, ChatGPT is not integrated into the WPML plugin. Our product team is aware of the interest in such a feature and is considering it for future updates.
