Problem: The client was experiencing issues with string translations not working correctly. The root cause was identified as a mismatch between the charset/collation settings in the config.php file and the database settings. Solution: We recommended the client to first ensure that all charset and collation settings in the config.php file match those of the database. Additionally, we advised the client to: 1. Visit WPML->Support->Troubleshooting and attempt to generate .mo files by clicking the appropriate button. If a popup does not appear, it might indicate a plugin conflict. 2. Disable all non-WPML plugins and switch to a default theme to check if the popup then appears. 3. Create a backup of the site (both files and the database) before making any changes. 4. Check the database for errors related to invalid data in tables, which might be caused by incompatible charset settings used by plugins like WooCommerce. For further details on resolving database errors related to charset issues, visit WPML support forum.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 issues persist, please open a new support ticket.
Problem: The client is experiencing a 503 error or a timeout when trying to access the 'Translate texts in admin screens' link in their WordPress site using the WPML plugin. This issue is accompanied by multiple WordPress database errors indicating that the 'wp_icl_background_task' table does not exist. Solution: First, ensure you have a backup of your site. Then, attempt to recreate the missing table by running the following SQL commands in your database:
DROP TABLE IF EXISTS wp_icl_background_task;<br />CREATE TABLE wp_icl_background_task (task_id bigint(20) unsigned NOT NULL AUTO_INCREMENT, task_type varchar(500) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL, task_status smallint(5) unsigned NOT NULL DEFAULT '0', starting_date datetime DEFAULT NULL, total_count int(10) unsigned NOT NULL DEFAULT '0', completed_count int(10) unsigned NOT NULL DEFAULT '0', completed_ids text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci, payload text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci, retry_count smallint(5) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (task_id)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
If issues persist after these steps, it may be due to other underlying problems not directly related to WPML. In such cases, we recommend checking for 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 still exists, please open a new support ticket for further assistance.
Problem: The client is unable to find the welcome email text for translation in the WCFM Frontend Manager and is facing issues with the translation of variable products not showing variations. Solution: To translate the welcome email texts, follow these steps: 1. Navigate to WPML-> Theme and plugins localization, select your theme/plugin, and scan. 2. Go to WPML-> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the needed strings. 5. Select the strings. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the strings, clear the cache, and check the front end. For more detailed guidance, check our guide on translating texts in the admin texts screen. Additionally, we need more information to assist with the variable product variations issue. Please provide your Debug information by following the instructions here: Provide Debug Information.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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, please visit our support forum at WPML Support Forum.
Problem: The client is experiencing issues with the 'Ultimate Member' plugin where translations are not being applied unless specific language files are removed. This issue persists even after downgrading WordPress to a version lower than 6.5, and updating plugins did not resolve the problem.
Solution: We recommend the following steps: 1. Ensure you have a full backup of your website and database. 2. Update WordPress, WPML plugins, all other plugins, and your theme to their latest versions. 3. If the problem persists, it appears that the 'Ultimate Member' plugin is not compatible with WPML. We suggest contacting the plugin author to request a compatibility update. You can provide them with resources to help achieve compatibility with WPML: - WPML support for developers - Achieving WPML compatibility for themes and plugins - WPML Go Global program
If these steps do not resolve your issue, or if the solution becomes 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 problem still persists, please open a new support ticket with us for further assistance.
Problem: The client is unable to change the link for the 'schedule an appointment' button at the top of their site, which is built with Elementor and managed with WPML. The button currently links to a Dutch page, but it should link to the corresponding English page. Solution: We found that the button is added through the 'Appearance >> Customize > Header builder' section. To update the link, we used the WPML String Translation tool. Here's how you can do it: 1. Go to WPML >> String Translation. 2. Search for the button URL. 3. Add the translation for the URL. This should update the button link to direct to the correct language version of the page. Please check to confirm that the changes are correct.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client is experiencing issues with variable products' translations not showing variations. Solution: If you're facing similar issues, we recommend you try the following steps: 1. Navigate to WPML -> Support -> Troubleshooting. 2. Run the functions one by one. Kindly check this documentation. 3. Edit the product in the default language. 4. Change the variation price and update the product. 5. Change the variation price back and update the product. 6. Update the product's translation. 7. Clear the site's cache and check the translated product on the front end.
Please ensure to backup your database before performing the above steps.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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: The client migrated to a new host provider and encountered issues with WPML plugins not working due to the site key not being validated. This issue arose because the domain name default changed with the new web host provider. Solution: We recommended the following steps to resolve the site key validation issue: 1. Perform a full site backup. 2. Navigate to your account page at https://wpml.org/account/sites/ 3. Delete the existing site key. 4. Go to Wp-Admin -> Plugins -> Add New -> Commercial tab. 5. Click on "Unregister WPML from this site". 6. Refresh the page. 7. Click on "Get a key for this site" and copy the newly generated code. 8. Return to Wp-Admin -> Plugins -> Add New -> Commercial tab and register the site with the new key. 9. Check if the issue persists.
The client's lifetime license allows registering multiple sites without additional costs for new site keys.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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: The client completed a purchase of 200K automatic translation credits but could not see the credits in their WPML account. Despite logging out and back in, the credits still did not appear. Solution: We verified from our side that the purchase was successful and the credits should be visible on the client's account page at https://wpml.org/account/. We suggested checking if the client might have another WPML account and to ensure they are logged into the account associated with their email address. Additionally, it was discovered that the 'Pay-as-you-go' option was active, which initially prevented the addition of prepaid credits to their site. After deactivating this option, the client was able to see and assign the credits.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client needed to change the publishing date of a translated article to match the date when the translation was actually published, but found that the date fields were locked and unchangeable in both 'edit' and 'quick edit' modes. Solution: We recommended the client to first ensure they are in the backend of the site and have switched to the desired language. They should then navigate to Posts or Pages, hover over the translated page/article, and select 'edit' or 'quick edit'. If using 'edit', the option to change the date should be available on the right sidebar. If a popup appears, they should select 'continue editing'. If the above steps do not unlock the date fields, we advised going to WPML > Settings and unchecking the 'Copy Publishing Date to Translations' option. After making this change, the client should make a small modification in the default language of the post to enable editing the date for the translated version.
If this solution does not resolve the issue or 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing an issue where loops are not appearing in other languages on your multilingual site, despite using 'pay-as-you-go' for translations and keeping the same category names. Solution: We recommend you navigate to WPML-> Settings-> Post Type Translation, and set the templates to
Translatable - use translation if available or fallback to default language
. After adjusting this setting, ensure to uncheck the automatic translation toggle.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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. Additionally, if you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is migrating their English content to a new domain and wants to display different logos for different language versions. Despite adding the English logo via Media Translation, it does not appear on the new English site, and changes affect both language versions. Solution: We recommended checking if the site's header was created using a template or a visual builder. The solution involved finding the URL of the logo in the admin texts section by following the steps in our guide on Finding Strings that Don’t Appear on the String Translation Page. After locating the URL, translating it to the English logo URL resolved the issue.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is using website management software that lists all available updates with links to the repository, but these links don't work for WPML because it is commercial software. The client requested adding links to the WPML release notes in the WordPress repository. Solution: We explained that WPML uses an installer plugin embedded within WPML itself, which manages updates. This process is complex and involves WordPress hooks and our remote server that provides the updates. The links in the Dashboard -> Updates section are generated by these hooks, and the update information is fetched periodically from our site and stored in the client's database based on their subscription.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client needs to set up a language switcher displaying only the language codes 'Ru En Ro' without flags or full names, as shown in their screenshot. Solution: First, ensure that the languages are set up in WPML by navigating to WPML > Languages. If not present, add new languages at WPML > Languages > Add new language. Detailed steps can be found in the documentation here: Editing WPML's Languages Table. Next, create a Menu Language Switcher by going to WPML > Languages > Menu Language Switcher > Create new language switcher and assign it to the desired menu. Make sure the current page is translated into the languages you want to display; otherwise, they won't appear in the switcher. To display only the language codes 'Ru En Ro', navigate to WPML > Languages > Edit languages and modify the language names accordingly. Then, adjust the settings in WPML > Languages > Menu Language Switcher or Footer Language Switcher to hide flags and show only the language names. For more detailed instructions on setting up the language switcher, visit: Language Switcher Options.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client reported that the Cookie Consent pop-up, which used to display in the language of the website page as translated in WPML Strings, now remains in English even when switching languages. The client suspected a change in functionality, possibly related to browser language settings. Solution: We clarified that the issue was not related to browser language settings but was due to a change in the string name by the Blocksy theme. We advised the client to check the Admin screen section of String Translation to see if the texts are listed there and to register them for translation if found. For detailed steps, we recommended following this guide: Translate Admin and Settings Strings. If the strings were not visible, we suggested updating the MO files by following these steps: - Go to WPML > Support > Troubleshooting. - Scroll down and click on the 'Show custom MO Files Pre-generation dialog box' button. - After the page refreshes, click on the 'Generate MO files' button and wait for the process to finish. - Clear the caches from the site and browser, then check again.
If this solution does not resolve the issue or seems outdated, we 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. If the problem persists, please open a new support ticket.
Problem: If you're experiencing issues with translating text within curly braces ({{}}) using the Heading widget from "Elementskit" in Elementor, it's because this syntax is not supported by WordPress or Elementor for focusing text. Solution: We recommend replacing the {{text}} notation with
<span>text</span>
. Text wrapped in tags will inherit the focused title settings and can be translated correctly. You should apply the same HTML formatting in the Translation Editor. For detailed guidance on using HTML in translations, please check this guide.
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. Should you need further assistance, please feel free to open a new support ticket at 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
