Problem: The client needs to know if there is a setting in WPML that allows updates made in the original language, such as adding a photo to a page, to be automatically visible in all translated versions of the page. Solution: We informed the client that the steps they are taking to update the translated content are correct. Currently, WPML does not offer a way to automatically update translated content when changes are made to the original language. Each translated page must be edited individually to reflect the changes.
If this solution does not seem relevant to your situation, please feel free to open a new support ticket with us.
Problem: The client wants the language switcher to only appear on the Malay language version of their website. Solution: If you're experiencing this, we recommend you use CSS to hide the language switcher from specific pages or languages. You can find detailed instructions on how to do this in our documentation on how to display or hide the language switcher on specific pages.
Specifically, you'll need to use the CSS :lang() Selector to target the menu item in the default language and hide it. You can find more information about the :lang() Selector here: MDN Web Docs.
Problem:
If you're trying to trigger Translate independently programmatically and need to delete all entries in the
wp_postmeta
table with the
_icl_lang_duplicate_of
meta key, Solution:
We recommend using the following SQL query:
DELETE FROM wp_postmeta WHERE meta_key = '_icl_lang_duplicate_of';
Before executing this query, please ensure that:
1. You have a backup of your database.
2. You understand that this operation is irreversible and will permanently delete these entries.
3. You have the necessary permissions to perform
DELETE
operations on your database.
If you're not comfortable with these operations, we advise consulting with a database administrator or someone with expertise in WordPress databases.
Problem: The client is experiencing issues with translating the English version of the product list on their WooCommerce shop. The filter appears in English, but the footer and "details" buttons do not. The footer consists of different strings, texts, and links. While the English front page displays correctly, the WooCommerce shop products page does not show the correct translations in the footer, and the "details" button is still in Danish. Solution: If you're experiencing similar translation issues with your WooCommerce shop using Oxygen templates, we recommend you follow these steps: 1. Update all WPML plugins. 2. Update the Oxygen plugin. 3. Update WooCommerce plugins. 4. Navigate to
WPML-> Settings-> Post Type Translation
. 5. Set the "Templates (ct_template)" post type to
Translatable – use translation if available or fallback to default language
Problem: If you're experiencing an error stating "There is a problem connecting to automatic translation. Please check your internet connection and try again in a few minutes," and you have identified that the WP External Links plugin is causing this issue when enabled, we can help.
Solution: We recommend adjusting the settings of the WP External Links plugin. Go to WP External Links > Exceptions > Apply settings on: 1. Disable "All contents (the whole page)" 2. Enable "Post content" and "Comments"
This should resolve the connection issue with automatic translation. Additionally, since the WP External Links plugin is not currently on our list of compatible plugins, we suggest reaching out to the plugin author and asking them to join our Go Global program. Our Compatibility developers will assist them in making their product compatible with WPML.
Problem: The client was unable to activate a new WPML license on their site, receiving the error 'Unable to parse subscription data from service.' This suggested that WPML could not communicate with the WPML server.
Solution: 1. We asked the client to provide a screenshot of the issue to confirm the error message. 2. We considered that the client's server IP might be blocked from our end. 3. The client provided their server IP obtained via
wp_remote_post
and the
$_SERVER['REMOTE_ADDR']
. 4. We checked with our systems team to see if this IP was blocked. 5. We manually updated the plugin for the client and were able to activate the site key without further issues.
Problem: If you're trying to translate a template and using block theme, but the translated template is not showing and being applied on the translated page check next solution. Solution: We have identified this as a known issue and are working on a permanent fix. Meanwhile, here's a workaround that should help: Follow these steps: - Remove the translated template. - Enable Slug Translation in WPML > Settings (Page URL > Translate). - Navigate to
Problem: The client is trying to link a page that is a translation of another page but cannot find the 'Connect with translations' button. Solution: We recommend checking the secondary language page in Edit mode, as the 'Connect with translations' link should appear there, not on the default language page. In this case, the secondary language seems to be French, so the client should open the French version of the page in Edit mode to see if the link is visible.
Problem: The client is experiencing an issue where the product image on the English version of their website is not updating correctly. After changing the image and saving, the old picture from the Slovenian/original version reappears upon page reload. The images appear in the WPML Media Translation but are not assigned to the English products.
Solution: 1. Confirm that the translated image is added as a translation of the default image in the WPML > Media Translation section. 2. If the image is added correctly and the issue persists: - Open the default product and add the image again. - Save the changes and update the translation. - Navigate to WPML > Settings and scroll down to the Media Translation section. - Click on the Start button, ensuring that the options above the button are selected. - Wait until the process is completed. This should resolve the issue of incorrect image assignment in the translated version. 3. After uploading the translated image, look for a notification at the top prompting you to scan and replace the image. Click on the button following the upload. 4. For a detailed guide on translating media files, visit the WPML Media Translation documentation.
If this solution does not seem relevant to your issue, please open a new support ticket with us for further assistance.
Problem: The client was experiencing issues with translating a product, receiving a message that WPML failed to translate the page three times. Additionally, there was a problem with being redirected to the translation queue after adding a new translation, and the new translation not showing any variations. Solution: 1. We recommended following the steps in the guide to resolve the translation error message: Translation status stuck or displaying the error 'WPML didn't manage to translate this page'. 2. If the problem persisted, we suggested trying the solution in the forum post: Unable to open translation page. 3. For the issue of being redirected to the translation queue, we advised checking the "WPML > Translation Management > Translators" tab to ensure the language pair is set up correctly and, if necessary, removing the profile from the Translator list if the client is an Admin. 4. If the redirection issue continued, we suggested a workaround mentioned in the Errata: Clicking on the translation icon redirects to WPML Translations instead of ATE.
We also reminded the client to take a full backup of the site before proceeding with any changes. If these solutions do not seem relevant, we encourage opening a new support ticket for further assistance: WPML support forum.
Problem: The client encountered a database error while trying to save changes on a Norwegian translated page in WordPress, with a message prompting to contact WPML support for a fix.
Solution: If you're experiencing a similar issue, we recommend the following steps: 1. Try to remove the warning message by clicking the small 'x' icon on the message. 2. Refresh the dashboard to see if the warning message reappears.
If the message does not reappear, the issue is likely resolved. However, if the problem continues, please let us know so we can investigate further.
For more information, please refer to our documentation on how to deal with error messages about a broken table:
Problem: The client is trying to translate the image caption in a carousel that was added using the Spectra Pro theme. Solution: We recommend the following steps to translate the image caption in the carousel: 1. Go to the page with the carousel and click "Edit Page" from the WordPress top bar. 2. Navigate to the carousel section and click on it to reveal the image text, as shown in the attached image. 3. Edit the text and update the page. 4. Switch the language of the page using the language switcher in the WordPress admin top bar to translate for other languages.
If these steps do not resolve the issue, we suggest setting up a staging site and providing us access to it, so we can further investigate without affecting the live site.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client experienced an HTTP 500 error after upgrading the WPML Multilingual CMS plugin and is hesitant to reinstall it due to fear of the error recurring.
Solution: 1. Ensure to back up the entire site for safety. 2. Increase the WordPress Memory Limit to at least 128MB, which is the minimum requirement for WPML, by adding the following code to the top of the
3. Update WordPress to the latest version for improved performance and stability. The latest version can be found at WordPress Releases.
4. Update the Divi theme to the latest version, which can be found at Divi Changelog.
5. Ensure all other plugins are updated to their latest versions.
6. Update WPML plugins to the latest version by going to the Plugins >> Add New page, clicking the Commercial tab, and then clicking the “Check for updates” button.
Problem: The client is experiencing issues with the order of product variations appearing differently in the translated version of their WooCommerce site. Additionally, there are problems with attributes not being synchronized and deleted attributes still appearing in translations.
Solution: 1. Navigate to WPML > Settings and locate the Custom Term Meta Translation section. 2. Search for "Order" and set the translation preference for terms starting with
order_pa
to "Copy". 3. Go to Products > Attributes, use "Quick Edit" below the attribute, and save without changes to copy settings to the translated product. 4. Visit WooCommerce > WooCommerce Multilingual > Attributes, select the attribute, scroll down, and click on Synchronize attributes and update product variations. 5. If issues persist, go to WooCommerce > WooCommerce Multilingual > Status, click on the Troubleshooting link, and start the following: - Sync product variations - Fix translated variations relationships
Remember to update the translation of the product after making changes to ensure that the translated versions reflect these changes accurately. If the attribute synchronization process takes an unusually long time, it may be due to a large number of products associated with the attribute.
If the solution provided does not seem relevant or if further issues arise, please do not hesitate to open a new support ticket with us.
Problem: The client is experiencing an issue where the language switcher for Chinese does not show up in Google Chrome, but it appears in Safari. Solution: If you're experiencing a similar issue where the language switcher is not visible in certain browsers, we recommend adding the following CSS to the custom CSS section of your theme:
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
