Problem:
Trying to translate the filters. All of the attributes are translated, and page and HTML blocks are translated, yet in the French language only the translated Filter button appears, but two filter fields with attributes are not appearing.
Problem: The client wants to remove the hreflang tag from specific non-indexable pages, such as the privacy policy page. Solution: We recommend disabling hreflang tags for all pages and languages by going to WPML > Languages > SEO Options. Currently, it is not possible to remove hreflang tags from specific pages using WPML settings; this action would remove them from all pages. Instead, for non-indexable pages, we suggest marking them as no-index, which can be done with the Yoast SEO plugin.
Please note that this solution might be outdated or not applicable to your case. If so, we encourage you to open a new support ticket for personalized assistance. 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.
Problem: The client reported that the menu language switcher disappeared from their website, while the widget language switcher was still visible. Additionally, they were concerned about the WP memory limit and its impact on their website. Solution: For the disappearing language switcher, we advised the client to check the configuration in WPML > Language > Menu language switcher and ensure that the 'Menu' is set to 'Menu no countries'. We also suggested verifying that the navigation menu is assigned to the correct 'Display Location' in their website settings. Regarding the WP memory limit, we explained that increasing the limit is crucial to prevent potential crashes due to insufficient memory when the website grows and more scripts from plugins and themes are loaded. More information on this issue can be found here: https://www.wpbeginner.com/wp-tutorials/fix-wordpress-memory-exhausted-error-increase-php-memory/
If this solution does not resolve your issue or seems irrelevant, we recommend opening a new support ticket. It's also advisable to 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.
Problem: The client wants to duplicate the German language setup for a new Austrian language version on their website, including duplicating strings and taxonomy data, and managing PO/MO files for translation. Solution: 1. To duplicate content from one language to another, follow the steps outlined in this forum post. 2. Strings cannot be duplicated directly; they must be translated. Manual translation can be done following the guide here: String Translation. Alternatively, use automatic translation for bulk operations as described here: Automatic Translation. 3. For syncing taxonomy data, refer to this forum discussion. 4. To manage PO/MO files, export the German translations and import them for the Austrian language as detailed here: Import/Export PO. Note that this process needs to be done per text-domain, which might be time-consuming.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: After moving the site to a new hosting provider, the client encountered an error stating 'WPML plugin cannot connect to wpml.org' due to a site key mismatch. Solution: If you're experiencing this issue, we recommend you follow these steps: 1) Ensure you have a full backup of your site. 2) Navigate to your Site Dashboard, go to Plugins>>Add New>>Commercial. 3) Click on the Unregister WPML from this site button. 4) Visit WPML.org, go to My Accounts>>Sites, and delete the existing site key. 5) Create a new subscription key for your site 6) Return to your Site Dashboard, go to Plugins>>Add New>>Commercial, and register with the new site key. 7) Refresh the page. For more detailed instructions, please check these tutorials:
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to set an ACF called custom_test to be translatable, but when you set it to translate and then edit the field in the post editor, the ACF reverts back to COPY instead of translate. Solution: First, ensure that the field is set to "Translate" instead of "Copy". You can do this by navigating to "Custom fields > Field groups" or by going to "WPML > Settings > Custom Fields Translation" to edit the translation preference for that field. For detailed guidance, visit the WPML documentation on setting translation preferences for ACF fields: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#setting-translation-preferences-acf-fields.
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 the problem persists, please open a new support ticket at https://wpml.org/forums/forum/english-support/ for further assistance.
Problem: The client was experiencing an issue where the images for product categories were not appearing in the translated versions and were instead showing a WooCommerce placeholder image after using automatic translation.
Solution: First, we recommended that the client update all outdated plugins and themes to ensure that all functionalities are up-to-date. If the issue persisted, we identified that the custom field for the category thumbnail and the media settings were not set up correctly. To fix this, we: 1. Went to WPML -> Settings -> Custom Term Meta Translation and set the
'thumbnail_id'
to
'Copy'
, then saved the changes. 2. Re-saved the permalinks at Settings -> Permalinks. 3. Ran the troubleshooting steps available in the WPML troubleshooting page. 4. Edited and saved a product category to update the translation.
We also suggested a workaround that involved creating a test product, adding all categories to it, translating the product, and checking if the categories were updated.
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 at our support forum.
Problem: The client is seeing an administrator notice in WPML but cannot find the button to resolve it. Solution: If you're experiencing this issue, we recommend you follow these steps after ensuring you have a backup of your database: 1. Open your database manager, such as PhpMyAdmin. 2. Navigate to the "wp_options" table. 3. Search for the 'icl_admin_messages' key using the following SQL query:
SELECT *<br />FROM `wp_options`<br />WHERE `option_name` LIKE '%icl_admin_messages%'<br />LIMIT 50;
4. Delete this key. 5. Refresh your dashboard to check if the message persists. Additionally, ensure that all your plugins, especially WPML and WordPress core, are up to date to avoid conflicts. You can download the latest version of WPML from here.
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: The client needed assistance with translating the term "Webstreet Shop" on their shop page created with the Divi Theme Builder. Despite translating the page and terms in "String Translation", the term did not appear translated on the website. Solution: We advised the client to ensure that the Divi template for the shop page is translated. We provided a step-by-step guide on how to translate Divi templates, which can be found here: https://wpml.org/documentation/theme-compatibility/divi-builder/#translating-custom-global-header-footer.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the 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 do not hesitate to open a new support ticket with us.
Problem: The client wants to export all translations to an Excel file and import them once translated. Additionally, the client is experiencing an error 524 due to a timeout when trying to load over 921 translations added to the translation basket, even after increasing the WP memory limit to 400M. Solution: To export translations to an Excel file, we recommend following the instructions provided by our colleague in a related support ticket, which can be found here: https://wpml.org/forums/topic/how-to-generate-a-clean-excel-file-for-external-translator/. Regarding the error 524 and the translation basket issue, we have created a separate ticket to address this problem. You can follow the progress and find the solution here: https://wpml.org/forums/topic/split-how-can-i-reset-translation-basket/. Please mark the current ticket as resolved.
Please note that the solution provided 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 do not hesitate to open a new support ticket with us.
Problem: The client is working on a custom theme using Advanced Custom Fields (ACF) and has encountered an issue where after entering a password on a password-protected page, it redirects to a 404 page instead of displaying the content. Solution: We recommend navigating to WPML->Settings->Login and registration pages and unchecking the option Allow translating the login and registration pages. This should resolve the issue and allow the password-protected content to display correctly after the password is entered.
If the client wishes to use the option to translate the login and registration pages, we advise reviewing the following documentation, especially since the client is on an NGINX server:
If the provided solution is not relevant due to being outdated or not applicable to your case, we suggest opening a new support ticket. We also 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 contact us in the WPML support forum.
Problem: The client is trying to change the slug for products in the French version on their WooCommerce site but the changes are not taking effect. The products in the French version appear to be duplicates of the English version, and there are concerns about SEO optimization and duplicate content.
Solution: 1. Ensure the slug is updated in WooCommerce > WooCommerce Multilingual > Store URLs. After updating, resave the permalinks. 2. If the issue persists, go to WPML > String Translation, search for the original slug, and remove it. Then, try updating the slugs again from WPML > Settings > Post Type Translation > Products. 3. To display only translated products and avoid duplicates, go to WPML > Settings > Post Type Translation, find Products, and set the translation preference to "Translatable - only show translated items". 4. The slug 'acheter' was already in use for product category base translation, causing a conflict. We resolved this by renaming the category base slug to
acheter-1
, which allowed the French product URLs to work correctly. A different slug should be used for the French category base translation.
Problem: The client is having issues with the WPML plugin not automatically loading existing .po/.mo files for plugins such as Events Manager. Additionally, the client is unable to see the country flag options on the Events pages, even after loading strings into the WPML system.
Solution: 1. WPML should automatically load .po/.mo files if they exist for a plugin and are in the correct language. If the translations are not working, the client can regenerate the .mo files through WPML by navigating to WPML -> Support -> Troubleshooting and using the relevant option.
2. Importing .po/.mo files alone will not display flags for Events in other languages. The client needs to translate the Events themselves or use a fallback option for displaying untranslated content in secondary languages, which can be found here: Displaying Untranslated Content on Pages in Secondary Languages.
If the provided solution does not apply or is outdated, or if the issue persists, 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.
Problem: The client needed to translate the "I've read and agree to the terms & conditions" acceptance text on the WooCommerce checkout page but was unable to find the correct string to translate. Solution: We recommended several steps to locate and translate the string: 1. Search for the string in WPML > String Translation. Helpful documentation on using the String Translation plugin can be found here: String Translation documentation. 2. If the string is not found, scan the theme or plugin generating the string for translations, as explained here: Theme Localization documentation. 3. Check if the string is an admin text and follow the process for finding and translating admin text strings: Finding and translating admin text strings. 4. Enable the "Look for strings while pages are rendered" option at the bottom of the WPML > String Translation page, visit the front end where the string appears, and then search for it again in String Translation. 5. If the string is hard-coded in the theme files, refer to this guide for translating: Translating hard-coded theme strings.
If these steps do not resolve the issue or if the solution is outdated or not applicable to your case, we encourage you to open a new support ticket. We also highly recommend checking related known issues at WPML 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 contact us on the WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
