Problem: If you're experiencing issues with double slashes (//) in your URLs for custom post types, which are being flagged as hreflang issues in your site crawls, this might be related to WPML's redirection functionality. Solution: First, verify if the double slashes appear when WPML is deactivated. This will help determine if the issue is directly caused by WPML or if it exists independently of it. If the double slashes still appear with WPML deactivated, the problem does not originate from WPML. It's also important to note that WPML correctly adds hreflang tags, and the issue of double slashes should not be confused with hreflang problems. If you need further clarification on why double slashes are flagged as hreflang issues by specific tools, you should contact the tool provider directly.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific case, 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 needed to change a taxonomy called "Location" to be global and not translatable. However, after making this change, updating the "Location" categories in the primary language post did not update the categories in the translated posts as it did before. Solution: We recommend setting the "Location" taxonomy to "Translatable" to enable synchronization across translated posts. If the taxonomy is set to "Not translatable", the synchronization of categories will not occur. For more information on how to set taxonomy terms to be translatable, please visit our documentation: Translating Post Categories and Custom Taxonomies.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket with us.
Problem: The client wanted to separate English into en_us and en_gb variations, with en_us as the default language and its URL changed from domain.com to domain.com/en_us/. They also wanted to implement en_gb at domain.com/en_gb/ while keeping all other languages unchanged. Solution: We advised the client that it is not possible to change the language code directly. Instead, we recommended creating custom languages with the en-us and en-gb codes. We instructed the client to: 1. Create a full backup of the database and website. 2. Follow the guide to create the en-us language and duplicate the content to the new language: https://wpml.org/faq/how-can-i-assign-or-change-language-code-to-existing-content/ 3. Add the language with the en-gb code by following this guide: https://wpml.org/documentation/getting-started-guide/language-setup/editing-wpmls-languages-table/#adding-your-own-languages-using-wpmls-gui 4.Kindly note that you'll also need to use a different locale for the en_us language because this locale is already used for the default English language. Please check this errata page Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, 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 you still need assistance, please open a new support ticket: https://wpml.org/forums/forum/english-support/
