Problem: The client is experiencing an issue where the WPML plugin cannot connect to the host after updating, and the website address appears different than expected. Solution: 1. We suggest that the issue might be a false positive due to server caching. The notification may be removed automatically when the cache clears. 2. To verify if it's a false positive: - Navigate to Plugins > Add new > Commercial. - Click the "check for updates" button. - If the page refreshes and WPML still shows as registered, then it's confirmed to be a false positive. If this solution doesn't seem relevant to your issue, please open a new support ticket with us.
Problem: The client needed to check if WPML was installed on a demo site that is no longer accessible and wanted to know how to remove it from their account if it was. Solution: 1. We recommend visiting your WPML account and clicking on "Register WPML on your sites" at https://wpml.org/account/sites/. 2. Look for your demo site in the list of registered sites. If you find it, click the trash icon to unregister it. 3. If the demo site is not listed, then it's not registered and there's no action needed. If this solution doesn't look relevant, please open a new support ticket.
Problem: The client is experiencing a PHP Fatal error when trying to save a page, with the error indicating an issue with the
array_filter()
function in the WPML plugin files. Solution: If you're experiencing a similar issue, we recommend you try the following steps: 1. Go to WPML → Support → Troubleshooting. 2. Run the option "Remove ghost entries from the translation tables". Please ensure you backup your database before making any changes.
Problem: The client needs to connect pages that are translations of each other after importing content from an old site. Solution: We recommend using the 'Connect with translations' feature to link pages that are translations of each other. Here are the steps to follow: 1. Go to the page that you want to connect. 2. Look for the 'Language' box on the right side. 3. Click on the 'Connect with translations' button. 4. A popup will appear where you can search for the page in the other language. 5. Connect the pages by selecting the appropriate translation. For detailed instructions, please refer to our documentation: How to link already translated pages.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
Problem: The client is experiencing an issue where the Korean version URL is being displayed in an encoded format when copying and pasting. Solution: We explained that browsers have a feature that encodes URLs to ensure they are usable and can be accessed without issues, especially if they contain specific characters. To copy the URL as it appears, we suggested omitting one letter from the protocol part of the URL, such as 'h' from 'https', and then adding it back after pasting.
Problem: The client is trying to retrieve all posts for a single language code using WP_Query and WPML filters, specifically for the default language code 'en'. The provided code with the
and the custom function did not work, as it still retrieved posts in all languages.
Solution: We recommend using
'suppress_filters' => false
in the WP_Query arguments. This will ensure that the query retrieves posts in the current language when on the English version of the website. For further optimization, the client can specify the fields they want to retrieve, such as 'ID', 'post_title', and 'post_content'. For more information on debugging theme compatibility with WPML, please visit: Debugging theme compatibility with WPML. Additionally, for WPML hooks reference, check out: WPML hooks reference. For WordPress reference on get_posts, please see: WordPress get_posts function.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
Problem: If you're trying to send pages to a translator for review and editing, but find that every time you add a job to the translation basket and assign a translator, it is immediately marked as complete without displaying a review button, the issue might be related to the page already being translated.
Solution: We recommend checking if the page you're trying to send for translation has already been translated. If you used the duplicate option to create the page, it's possible that the translation was duplicated as well. To resolve this, create a new test page using the duplicate option, then delete its translation and remove it from the trash. After doing this, try adding the job to the translation basket and assigning a translator again. You should now see that everything works as expected, and the review button should be available in WPML → Translations.
If this solution doesn't look relevant to your issue, please open a new support ticket with us, and we'll be happy to assist you further.
Problem: The client is using the WPResidence theme, which is translated into Portuguese, and now they want to translate it back into English. They are encountering issues where English translated properties are showing up in the Portuguese list and custom PHP values are not being transmitted correctly. They are unable to find the strings for 'area' and 'quartos' in WPML, and there are issues with custom links, search buttons, and taxonomy terms appearing in the wrong language.
Solution: 1. To change the string language, select the string and change the language of the string using the option in WPML's String Translation interface. 2. To translate theme options, search for the strings in the WPML String Translation page and add them to the string translations. Once added, they can be translated into another language. 3. Update and re-translate the page to English in WPML, ensuring that the values are copied over correctly.
Problem: The client is experiencing issues with translating strings and has received an error after upgrading WooCommerce to version 8.3. The client had previously solved a problem by rewinding the server. Solution: We recommend increasing the memory limits and execution time by adding the following custom PHP code to the
wp-config.php
file on your server:
ini_set('memory_limit', '512M');
ini_set('upload_max_filesize', '512M');
ini_set('post_max_size', '512M');
ini_set('file_uploads', 'On');
ini_set('max_execution_time', '3600');
define('WP_MEMORY_LIMIT', '512M');
If this solution doesn't look relevant or if you continue to experience issues, please open a new support ticket with us.
Problem: The client was unable to translate some custom added post types. Clicking the '+' to add translations loaded a blank page, with Safari reporting 'Safari can’t open the page' and Chrome showing an 'ERR_EMPTY_RESPONSE' error. Solution: 1. We installed the WPML SEO addon plugin to ensure compatibility. 2. We disabled and then re-enabled the Yoast SEO and Yoast Duplicate plugins. 3. We cleared the WPML cache. Additionally, we noted that some errors might be related to the use of PHP 8.2.6, which isn't fully compatible with WordPress. We recommend checking the compatible PHP versions with WordPress here: WordPress and PHP Compatibility.
If this solution doesn't look relevant, please open a new support ticket in the WPML support forum.
Problem: The client is experiencing issues when clicking the 'Translate Link Targets' feature on their website, which seems to create a mess in the content. Solution: We explained that the 'Translate Link Targets' feature is designed to synchronize translated links with their translations if they exist. It was introduced to replace the 'Sticky Links' addon and is intended to be used once, typically after an import, migration, or a bug fix in the feature.
We also clarified the difference between 'Translate Link Targets' and 'Sticky Links':
'Sticky Links' converts all links to a default format when saving a post (e.g.,
?p=123
) and then converts them back to normal links (e.g.,
/hello-world/
) when displayed on the frontend.
'Translate Link Targets' is a newer feature that is always enabled and is used by everyone, unlike 'Sticky Links' which is an older plugin and not widely used.
We recommended that if the client is using page builders and experiencing problems with 'Translate Link Targets', they should avoid using it completely.
Now, the problem should be solved, and while on the checkout page, when you switch to a country other than Sweden, the currency will change. Please be aware that the suggested workaround might have other effects we are unaware of.
Problem: The client is encountering a fatal error when trying to update the WPML plugin, indicating a database issue with missing AUTO_INCREMENT on tables and primary keys.
Solution: 1. We recommend installing a database management plugin like WP-PhpMyAdmin to inspect the database. 2. Check and ensure that AUTO_INCREMENT is set on all default WordPress tables and WPML tables. This includes tables like
wp_usermeta
,
wp_terms
, and
wp_icl_strings
. 3. If there are missing primary keys and indexes on WPML tables, these need to be fixed as they indicate a general database problem. 4. Consider the number of translations already done on the site. If there are not many, a WPML reset might be an option. Instructions for a WPML reset can be found here: WPML Reset Documentation. 5. If the issue persists, restoring a backup of the site before the error occurred is recommended. Check the database structure, including AUTO_INCREMENT settings, before attempting to update WPML again. 6. Compare the structure of your site's database tables with a correctly set up WPML installation using the sandbox site provided: Sandbox Site.
Problem: The client was unable to find strings for translation in RevSlider, even after enabling the option in RevSlider and it being visible in WPML.
Solution: We recommended creating a separate slider for each language instead of looking for strings to translate. This process is detailed in our documentation on Creating Multilingual Sliders with Revolution Slider and WPML. We have set the slider's language to Polish for the client, and they can now duplicate it and manually change it to English.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive