Problem: The client is experiencing an issue where the 'Translation Tools' tab in WordPress does not display properly, showing signs of CSS not loading and a malformed URL causing a 404 error when trying to load a CSS file. Solution: We recommend the following steps to resolve the issue: 1. Perform a full backup of your WordPress site. 2. Disable all plugins except those related to WPML from your WordPress Dashboard > Plugins, and check if the issue resolves. If the issue disappears, reactivate each plugin one at a time to identify the conflicting plugin. 3. Temporarily switch to a default WordPress theme, such as 'TwentySeventeen', via your WordPress Dashboard > Appearance > Themes, to see if the issue persists. If these steps do not resolve the issue, it may be necessary for us to take a closer look at your site. In this case, we would require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated. Please ensure to back up your site using tools like UpdraftPlus.
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 the issue persists, please open a new support ticket.
Problem: You are using WPML with the default language set to German and a secondary language of English, and you want to configure WPML so that automatic translations use British English (en_GB) instead of American English (en_US). You are unsure if automatic EN-GB output is possible or if the system defaults to EN-US for automatic translation. Solution: Currently, WPML does not support a separate option for British English (en_GB) in automatic translations; it defaults to American English (en_US). This limitation is not specific to WPML but is due to the capabilities of major automatic translation engines like Google Translate, DeepL, Microsoft Translator, and Amazon Translate, which only support a generic English version, effectively American English. You can check the currently available languages for automatic translation here.
If this solution does not apply to your case, or if it seems outdated, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client is experiencing an issue with duplicate URLs appearing in the XML sitemap generated by Yoast SEO on a website using WPML SEO. Specifically, URLs for the same slugs appear in multiple sitemaps with and without language prefixes. Solution: We discovered that the issue was not directly related to WPML or Yoast SEO configurations but was due to a problematic content import process. Here are the steps we took to resolve the issue: 1. We identified that the duplicate URLs were linked to blog posts imported incorrectly. 2. The client had run the import process twice due to initial failures in matching translations, which created duplicate entries. 3. We advised the client to delete the first set of imported files and the associated blog posts, which were still present on the server despite not being visible on the frontend. 4. After removing these files and posts, the duplicates in the XML sitemap were successfully eliminated.
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, 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: You are trying to view the Translation Dashboard on your site but encounter an error message indicating that the REST API test endpoint is not responding correctly, despite it being valid when tested. Solution: We moved your site to a minimal environment, switching the theme to 2024 and deactivating all plugins except WPML. This process helped us identify that the WP-Ban plugin (https://wordpress.org/plugins/wp-ban/) is causing the issue. This plugin has not been tested with the latest three major releases of WordPress and is not officially compatible with WPML. We recommend deactivating the WP-Ban plugin to resolve the error.
If this solution does not apply to your case, or if it becomes 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 open a new support ticket at WPML support forum.
Problem: The client was unable to display all available languages in the WPML language switcher on English pages, which is the default language. Despite enabling settings like 'Use directory for default language' and 'Always show languages (even if not translated)', and performing actions such as clearing WPML caches and re-saving permalinks, only English was displayed in the switcher. Additionally, the Menu Sync tool was returning a 500 error. Solution: We resolved the issue with the language switcher not displaying all languages by clearing the cache at the hosting provider, Kinsta. This action allowed the switcher to appear correctly in English. For the 500 error with the Menu Sync tool, we recommend checking server error logs for more details or increasing the PHP memory limit, as it might be related to server resource limits.
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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: After migrating a website from one server to another, the layout is damaged, and a PHP fatal error related to the WPML plugin occurs. The error message indicates an issue with
DOMDocument::loadHTML()
being called with an empty argument. Solution: 1. Manually upload fresh copies of the WPML plugins from your account at https://wpml.org/account/downloads/. 2. Temporarily disable all plugins except for the WPML plugin to check if the issue still occurs. 3. If the problem persists, provide temporary access (wp-admin and FTP) to a staging or test site where the problem can be replicated. Include exact steps to replicate the issue for more efficient investigation.
If this solution does not resolve your issue or seems outdated, we 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 necessary, please open a new support ticket at WPML support forum for further assistance.
