Problem: You are using the WPML translation tool, both ATE and automatic, and encountering an issue where the special character '»' (raquo) is being translated as quotation marks ('"') instead of its correct form. Solution: We have not been successful in persuading DeepL to address this translation issue differently. Although we plan to fix this on our end, it is not yet scheduled in any development cycle, which means a resolution might take some time. In the meantime, we recommend using a different translation engine for those pages or avoiding the use of angle quotes in this specific manner. For instance, using "this > that" does not present the same issue.
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.
Problem: You are trying to translate over 2,000 tags on your website automatically using WPML, but you find no option for this in the translation panel, unlike the option available for categories. Solution: We recommend creating a post and assigning all the tags you wish to translate to this post. Then, navigate to WPML > Translation Management > Dashboard and send the post for automatic translation. This method allows you to translate all tags at once. For a detailed guide on translating taxonomy terms, please visit https://wpml.org/faq/how-to-translate-all-taxonomy-terms-at-once/.
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, 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 at WPML support forum.
Problem: You are working on a multilingual site and have added a new language using WPML. While the posts are translated correctly, the slugs and URLs are not being translated. Solution: To enable or change the translation of slugs and URLs, you should adjust the permalink settings for translated content. Here are the steps you can follow: 1. Navigate to WPML → Settings. 2. Under Translated documents options, set the Page URL to "Auto-generate from title (default)". 3. Re-translate the affected posts/pages into the new language to ensure the new URL settings are applied correctly. For more detailed guidance, please refer to our documentation on translating page slugs.
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 further assistance is needed, please open a new support ticket.
Problem: The client was experiencing an issue where WPML was creating unnecessary URLs in the format /pl/ and /en/ for a website that uses different domains for each language version. This resulted in six versions of each page instead of the required two, causing server load issues.
Solution: 1. We reset the permalinks to "postname" to ensure that URLs like https://4659bb91.cfolks.pl/pl/malta redirect to https://4659bb91.cfolks.pl/malta. 2. We advised the client to use the "A different domain per language" option as detailed in our documentation here. 3. We investigated the permalink structure "/%category%/%postname%.html" and found it was causing issues with WPML redirection. We escalated the issue to our secondary support team for further investigation. 4. We recommended checking if the Permalink Manager Pro plugin could redirect the unnecessary URLs to the correct ones, thus resolving the issue.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking related known issues here, 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 here.
