Problem: The client is considering de-registering WPML from their website and is concerned about losing the accumulated translation credits. Solution: If you're considering de-registering WPML from your website, rest assured that you will not lose your translation credits. These credits will remain in your WPML.org account and can be reused if you decide to register WPML on the same or a different website in the future. For more details on how credits can be assigned or removed, please visit how to assign automatic translation credits to your sites. Additionally, when you remove a key from here, the credits assigned should automatically move back to your WPML.org account.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client reported that after translating their site from English to Russian, all Russian translations were displayed as question marks across the site. Solution: We identified that the issue was due to the database encoding not being set to UTF-8. We recommended the following steps: 1. Adjust the database tables to use UTF-8 encoding by executing the following SQL commands:
ALTER TABLE $table DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci
ALTER TABLE $table CHANGE $field_name $field_name $field_type CHARACTER SET utf8 COLLATE utf8_bin
2. Add the following line to the wp-config.php file to ensure the database uses UTF-8 charset:
define('DB_CHARSET', 'utf8');
3. Clear the WPML cache and fix WPML tables collation via WPML->Support->Troubleshooting. 4. If the issue persists, deactivate WPML temporarily and test creating a new page with Cyrillic letters. 5. For existing pages, re-save the translations or edit and update the pages without making changes to force a refresh of the content.
If these steps do not resolve the issue or if the solution 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 problem persists, please open a new support ticket.
Problem: The client has set up a news page and translated it into multiple languages. However, the language switcher on the posts page redirects to the homepage instead of the translated news pages. Solution: First, ensure that the News page is fully translated into all required languages. This can be checked in Pages>>All Pages, where each translation should display a pencil icon. If the issue persists, follow these troubleshooting steps: 1. Perform a full site backup. 2. Temporarily switch to a default WordPress theme (e.g., 2023 or 2024). 3. Deactivate all non-WPML plugins. 4. Check if the issue still exists. 5. If resolved, reactivate the plugins in groups of three or four to identify any that cause compatibility issues. 6. Revert to the original theme.
If these steps do not resolve the issue, it may be due to outdated solutions or specific circumstances not covered here. We recommend visiting our known issues page, ensuring you have the latest versions of themes and plugins, and if necessary, opening a new support ticket for further assistance.
Problem: After setting up a staging environment for the site and performing a search-replace operation, a warning appeared in the admin panel indicating a migration service error with the message 'Migration code expired, please generate a new one'. Solution: We recommend generating a new migration code. You can do this by navigating to WPML>>Translation Management>>Tools>>Connected sites>>Enter the connection key of another site. After updating the migration code, please try connecting the staging site with the live site again and let us know if the issue persists.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
If you use the Rank Math SEO plugin and its Remove base option in conjunction with WPML’s Different domains per language setting, this may lead to excessive redirections, resulting in the ERR_TOO_MANY_REDIRECTS error.
Solution:
Please make sure to have a full site backup of your site before proceeding.
1. Open …/wp-content/plugins/seo-by-rank-math/includes/modules/woocommerce/class-product-redirection.php file.
Problem: The client was experiencing issues with WPML on a new installation where the site immediately started loading 'EN' URLs without having English translations ready. Additionally, the site recognized the original Portuguese content as English, causing functionality issues when attempting to hide the 'EN' language. Solution: We recommended the following steps to resolve the issue: 1. Make a full backup of the site. 2. Navigate to WPML -> Languages -> Add / Remove languages, uncheck 'English' and save. 3. Go to WPML -> Support -> Troubleshooting and perform the following actions in order: - Clear the cache in WPML - Fix element_type collation - Fix WPML tables collation - Set language information - Reset languages 4. Check the option 'I am about to reset all translation and language data.' and click on 'Reset and deactivate WPML'. 5. Reinstall WPML, setting Portuguese as the main language and English as the secondary language.
After these steps, the issues were no longer reproducible, and the site functioned correctly with the correct language assignments.
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 problems persist, please open a new support ticket at WPML support forum.
Problem: After upgrading the WPML plugin, an error appeared in the PHP error log indicating that the table 'cordmagazine.wp_icl_background_task' does not exist. Solution: If you're experiencing this issue, we recommend you first log into your database to check if the wp_icl_background_task table exists. If it doesn't, please perform a full site backup before proceeding. After ensuring your site is backed up, you can try to resolve the issue by running the following SQL query in your database management tool like PHPMyAdmin:
DROP TABLE IF EXISTS `wp_icl_background_task`;
CREATE TABLE IF NOT EXISTS `wp_icl_background_task` (
`task_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT,
`task_type` varchar(500) COLLATE utf8mb4_unicode_ci NOT NULL,
`task_status` smallint UNSIGNED NOT NULL DEFAULT '0',
`starting_date` datetime DEFAULT NULL,
`total_count` int UNSIGNED NOT NULL DEFAULT '0',
`completed_count` int UNSIGNED NOT NULL DEFAULT '0',
`completed_ids` text COLLATE utf8mb4_unicode_ci,
`payload` text COLLATE utf8mb4_unicode_ci,
`retry_count` smallint UNSIGNED NOT NULL DEFAULT '0',
PRIMARY KEY (`task_id`)
)
This solution might be 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.
Problem: The 'read more' button on the Testimonials and Blog pages is not translating. Solution: If you're experiencing issues with the 'read more' button on your site, we recommend following these steps to potentially resolve the issue: 1. Navigate to WPML → String Translation. 2. Enable the option 'Look for strings while pages are rendered'. 3. Visit the page where the 'read more' button is not working. 4. Return to WPML → String Translation and check if the string for the 'read more' button has been registered. 5. If found, translate the string accordingly. For more detailed guidance, please refer to our documentation on finding and translating strings.
Please note that this solution might be outdated or not applicable 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. If the issue persists, please open a new support ticket.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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, you can also contact our support team directly at https://wpml.org/forums/forum/english-support/.
Problem: The client moved their site to a new hosting and changed the domain from test.jinshiyuan.sg to delightsip.com. After the move, WPML detected the new address as the old one, causing issues with site recognition. Solution: If you're experiencing this issue after moving your site to a new hosting, we recommend you follow these steps: 1. Click on YES in the message box regarding the site address change. 2. Set the website to not share credits. 3. Visit your WPML account and remove the existing keys at https://wpml.org/account/sites/ 4. In your website's admin panel, go to Plugins > Add New > Commercial Tab and remove the key. 5. Create a new key for your current domain (delightsip.com) at WPML.org. 6. Register the new key in the same location in your admin panel (Plugins > Add New > Commercial Tab). For more detailed instructions, you can check https://wpml.org/faq/how-to-remove-the-this-site-is-registered-on-wpml-org-as-a-development-site-notice/
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: If you're experiencing issues with the WPML translation editor not recognizing line breaks in posts created through the Classic Editor, where instead of seeing different translation zones for each paragraph, you see one big paragraph, we can help. Solution: We are currently working on a permanent fix for this issue in future releases. In the meantime, to address this for previously created content, you need to delete the existing translation and recreate it. Here’s how you can do it: 1. Ensure you have a full website backup. 2. Navigate to your Pages or Posts tab. 3. Change the language in the topbar by clicking on the flag and selecting a secondary language. 4. Find the translation, send it to the trash, and then permanently delete it from the trash can. By following these steps, when you create a new translation, it should adhere to the new settings and resolve the issue. If this solution does not resolve the issue, please visit this documentation.
Please note that this solution might be outdated or not applicable 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. If the problem persists, please open a new support ticket.
Problem: You are developing a site and trying to translate the 'add to cart' button but cannot find the relevant code in functions.php, despite following documentation. Solution: If you're experiencing this issue, we recommend checking our documentation on string registration to make the strings available for translation in the UI. Here are some useful links:
Please note that the solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing issues with losing translations of accordion content in DE/FR/IT languages when updating your homepage using WPML. Additionally, module IDs lose their translations when the page is updated. Solution: We have attempted to replicate the issue using a clean Sandbox environment with only WPML and Divi, using the imported homepage layout from your site. In this controlled environment, updating the title did not affect the translations in the Divi Accordions, suggesting the issue might be specific to your installation. We recommend providing us with a Duplicator copy of your site for further debugging.
Problem: The client experienced a PHP memory limit error during the installation of WPML and the String plugin, which led to a site crash. After resolving the initial crash by renaming and deleting plugins, the client faced issues with missing database tables and persistent PHP memory errors when JetEngine was activated. Solution: 1. Deactivate JetEngine to prevent PHP memory limit errors. 2. Upload and install WPML plugins. 3. Reactivate JetEngine after the installation. This sequence helps manage the PHP memory load during WPML installation. If you're experiencing similar issues, we recommend trying these steps. Additionally, ensure your hosting environment allocates sufficient memory, as outlined in our minimum requirements.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please check our known issues page and confirm that you have the latest versions of themes and plugins installed. If problems persist, we highly recommend opening a new support ticket here.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive