Problem: The client needed to adjust hreflang tags for
different regional versions of their website. Specifically, they wanted to
change 'en-usa' to 'en-us' and set regional codes like 'en-x-emea' and
'en-x-apac'. Additionally, they encountered issues where changes were not being
saved and received an error stating 'The hreflang already exists.'. Solution:
We advised that the hreflang formats like 'en-x-emea' or 'en-x-apac' can be set from WPML -> Languages by adjusting the hreflang as needed.
To resolve the issue of the hreflang not saving (because the Enlgish language was used before, and as a result the hreflang "en-us" was already set to it), we suggested:
1. Activate the default English language on WPML -> Languages.
2. Change the hreflang for the default English language if it was previously set to 'en-us'.
3. Save the changes.
4. Attempt to change the hreflang from 'en-usa' to 'en-us' again and save.
5. Remove the default English language on WPML -> Languages if no longer needed.
This process helped in correctly setting up the desired hreflang tags. If these steps do not resolve your issue or if the solution 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with their sitemap displaying pages that do not exist, specifically URLs containing "/en/" which were remnants of an old language setup. The client had already tried resetting Yoast sitemap and indexables without success.
Solution: We recommended the following steps: 1. Re-enable English as a language temporarily in WPML > Languages. 2. Manually delete all media, pages, custom posts, taxonomies, and menus associated with English using the WordPress User Interface and the language switcher. 3. Remove the English language again and run the cleanup dialog. 4. Check WPML > Settings > Post Type Translation to ensure that any post types that should not be translatable are set correctly. 5. If necessary, temporarily set certain post types (like ACF Field Groups) to 'Translatable' to delete specific entries, then revert them to 'Not translatable'. 6. Run a MySQL query to clean up leftover entries in the database:
DELETE FROM `wp_icl_translations` WHERE `language_code` = 'en'
If these steps do not resolve the issue or if the solution 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 the problem persists, please open a new support ticket.
Problem: The client is experiencing issues with deprecated function errors appearing on their site. Solution: We advised the client to ensure that their WordPress website is not set to display debug entries on the front end. To address this, we recommended editing the
wp-config.php
file and adding the following code before the
/* That's all, stop editing! Happy publishing. */
line. If there are any existing WP_DEBUG settings, they should be removed to avoid conflicts.
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );
Please make sure to have a full website backup before proceeding. We also mentioned that the WPML-related messages are just warnings and can be ignored. If the client has any further questions, they should let us know.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If after trying the suggested steps the issue persists, 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 the problem continues, please do not hesitate to open a new support ticket.
Problem: The client needs to set up three different regions for their site: EMEA (primary), North America/US, and APAC. Both EMEA and APAC should use British English, while North America/US should use American English. They want to use DeepL for translations but are facing issues with language mapping for different English variations. Solution: 1. We explained that automatic translation in WPML works based on language mapping settings. Since the site's default language is English, it cannot be automatically translated into other English variations (American or British English) using WPML. 2. For content in different English variations, the client will need to manually add translations using the Translation Editor. 3. We suggested that if the content is the same across the different regions, the client could duplicate the pages instead of translating them. 4. We also mentioned that WPML currently supports only one type of language per content, as shown here: https://ate.wpml.org/mt_langs
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you encounter issues or if the solution does not work for you, 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 was experiencing a significant slowdown of the WordPress dashboard after installing WPML on a site hosted on Pantheon. The dashboard was so slow that it was practically unusable, and the error 'The application did not respond in time' was occurring. The hosting support found slow PHP logs pointing to WPML functions.
Solution: First, we asked the client to enable WordPress debugging to gather more information about the issue. We provided instructions on how to modify the
Upon further investigation, we noticed a double slash in the URL within the PHP logs, which could be related to the issue. We advised the client to look into why the double slash was occurring and to resolve it, as debugging custom themes or plugins is beyond our support scope.
If the provided solution is not relevant due to being outdated or not applicable to your 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. If further assistance is needed, please contact us in the WPML support forum.
