Problem: The client is inquiring about the release date for WPML 5.0 as they are eager to move it to production after testing it on staging. Solution: We are currently in the final stages of testing WPML 5.0. We estimate that the final production version will be available approximately two weeks from now. We will keep you updated with any further confirmations.
Please note that this solution might become outdated or may not directly apply to your specific situation. If this is the case, we highly recommend checking the related 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.
Problem: The client reported an issue where they were unable to perform string translations, receiving an error stating they were not recognized as a translator despite being listed as one. Solution: 1. We requested the client to provide access credentials to their site to allow us to reproduce the issue and check the WPML configuration. 2. After gaining access, we added the names and last names to the translator users to resolve any conflicts with our servers. 3. We instructed the client to log out and then log back in to refresh their session. 4. We added English to the language pairs in the client's user account, which resolved the issue.
If this solution does not apply to your case, or if it seems outdated, 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 was unable to edit the 'Fragen & Antworten' page in WordPress, receiving a critical error message. Additionally, Kadence Navigation items could not be translated, displaying a red WPML banner indicating translation failure. Solution: 1. We suggested checking the PHP error logs for details about the critical error, but no relevant entries were found. 2. We advised modifying the
wp-config.php
file to enable WP_DEBUG and WP_DEBUG_LOG to capture any new errors. However, this did not resolve the issue as no new logs were generated. 3. We then directed the client to enable debug logging in the Advanced Translation Editor (ATE) and reproduce the translation failure. This revealed that the ATE job for 'Fragen & Antworten' was completed but not delivered, indicating a need for technical review. 4. For the navigation translation issue, we recommended editing each header and navigation item in the original language and then sending them for translation again through WPML -> Translation Management.
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 the problem persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is using the core post-terms block to list taxonomy terms for a custom taxonomy in a block theme and needs to translate the prefix "Audiences:" into different languages based on the site version. Solution: We recommend first re-saving the template to ensure that its content is properly stored in the database. Next, register the custom block for translation. You can follow the detailed instructions on how to make custom Gutenberg blocks translatable at this guide.
If this solution does not apply to your case, or if it seems outdated, 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. We highly recommend opening a new support ticket if further assistance is needed. You can do so at WPML support forum.
Problem: When attempting to update a specific page, the process spins indefinitely and results in a 502 error. This issue occurs only when WPML is enabled, even after updating WordPress core, all plugins, themes, and changing PHP versions. Solution: We recommend following these steps to resolve the issue: 1. Navigate to WPML → Support → Troubleshooting. 2. Execute the following troubleshooting actions: * Clear the cache in WPML * Remove ghost entries from the translation tables * Fix element_type collation * Fix WPML tables collation * Assign translation status to duplicated content * Set language information * Fix post type assignment for translations 3. Optionally, if the issue persists, run the option to repopulate the language information available on the same Troubleshooting page. After these steps, the issue should be resolved, and the page should update without triggering the 502 error.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check for any related issues. Ensure you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket at our support forum.
Problem: The client is unable to reconnect a manually recreated English post with its existing French translation in a bilingual site. The WPML tool does not recognize the connection, even though the post is published and the titles match. Solution: We recommend the following steps to resolve the issue: 1. Navigate to WPML → Support → Troubleshooting. 2. Execute these options: - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Fix WPML tables collation - Assign translation status to duplicated content - Set language information - Fix post type assignment for translations 3. After completing these steps, attempt to reconnect your translation.
If this solution does not resolve your 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client created an Avada layout where the embedded JavaScript does not run in the translated version. The script works on the Hungarian page but fails on the English page due to syntax errors caused by translation modifications. Solution: We recommend not adding JavaScript directly to an Avada Layout as translation tools may alter the script. Instead, add custom JavaScript through:
Avada’s Custom Code settings
A dedicated custom-code plugin
The child theme, specifically through its
functions.php
file
For the specific issue, the JavaScript on the English page had a backslash removed, making it invalid. This error can be fixed by moving the script outside the translated Avada Layout or by ensuring the same code is correctly pasted in the layout for the second language.
If this solution does not resolve your issue or seems outdated, please check related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket here.
Problem: The client reported multiple issues on their multilingual site using WPML: missing images on accommodation cards in different languages, raw JavaScript displayed as text, incorrect number of items per language, and mistranslation of dynamic price strings.
Solution: We recommended the following steps to address the issues: 1. For missing images and synchronization issues: - Deactivate Lazy Load and W3 Total Cache plugins. - Navigate to WPML > Settings > Media Translation. - Disable automatic media translation, synchronize all media, and then re-enable it. - Ensure featured images are synchronized in the post's edit screen. - Make a minor edit to trigger a translation update and save the post. 2. For raw JavaScript issues, avoid adding JavaScript directly inside Elementor widgets. Instead, use the Code Snippets plugin or a child theme. 3. For incorrect item counts and translation completeness: - Make a minor edit to the original post and update the translation to 100%. 4. For the dynamic price string issue, scan the MotoPress-related plugins under WPML > Theme and Plugins Localization to correct the translation. 5. To resolve caching issues affecting content display, clear server-side cache and ensure any object or Redis cache is also cleared. 6. Make the Accommodation Categories translatable under WPML > Settings > Taxonomy Translation and verify the changes on the site.
If these steps do not resolve your issues 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: While transferring blog posts from WordPress to Crowdin for translation using WPML, the FAQ section of blog articles is duplicated. The text appears in Crowdin both as fragmented translation units and as a complete translation unit with the correct inline formatting. This issue is caused by the Yoast FAQ block in the Gutenberg post editor, which stores the same answer twice: once as visible content split into pieces around the link, and once as a complete string for the schema. Solution: We recommend updating the WPML plugins to the latest version. You can update your plugins in Plugins -> Add new -> Commercial tab. Ensure all other plugins and themes, especially Yoast plugins, are also up-to-date. After updating, edit the FAQ page, make a small change to the content, save the changes, and then check if the XLIFF file shows the content without duplication. If the issue persists, please contact us for further assistance. We might need to write a custom XML or escalate the issue to our second tier of support.
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 continues, do not hesitate to open a new support ticket at WPML support forum.
Problem: When attempting to translate a page to Bulgarian using WPML, the client encountered an error stating that WPML tried to translate the page three times and failed. The Translation Dashboard indicated that the Bulgarian translation was already complete, preventing the client from sending the page for translation again. Solution: 1. Verify that the translation assignments allow for English to Bulgarian translation in WPML -> Translation Dashboard -> Manage Translators & Services. 2. If the client is assigned as a translator but the language pair is not enabled, they should reconfigure this setting. 3. If the client is an administrator, they should remove and re-add their translator assignment and save the changes. 4. Edit the original English page using Elementor, make a minor change, and save. 5. Go to WPML -> Translation Dashboard, assign the translations to themselves, and update the translation.
If this solution does not resolve the issue or seems outdated, or if it does not apply 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 was experiencing an error when switching from the Latvian (LV) to Lithuanian (LT) language on certain custom post type (CPT) product URLs after editing or removing the LV CPT URL slug. The issue was specifically tied to a user-created Avada template.
Solution: 1. We recommended refreshing the permalink structure by navigating to Settings -> Permalinks and clicking Save Changes without altering any settings. 2. We verified that the CPT translation settings were set to Translatable with translated slugs enabled. 3. We checked that Avada Builder and Avada templates were configured as translatable in WPML. 4. We suggested ensuring that the Lithuanian and Latvian versions of the affected items were linked as translations of one another. 5. If these steps did not resolve the issue, we advised the client to provide access for further investigation and possibly contact the support teams for the caching and security plugins, as the issue seemed related to outdated cached data or plugin configuration.
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 for personalized assistance.
Problem: The client is experiencing a database permission error with the message 'INSERT command denied to user '12txv_smr'@'172.22.44.87' for table 'wp_icl_strings''. This issue is tied to a specific, now-deleted post, and the database user '12txv_smr'@'172.22.44.87' does not have the necessary privileges, which differ from those at 'localhost'. The client is unsure about the origin of the '172.22.44.87' host and why permissions differ.
Solution: We recommend the following steps: 1. Inspect MySQL user privileges and ensure that '12txv_smr'@'172.22.44.87' can INSERT into
wp_icl_strings
. 2. Determine why some connections use 'localhost' and others use '172.22.44.87'. This may involve reviewing the database connection routing, proxy, or container setup. 3. Adjust privileges or configure the site connections to use the correct MySQL host identity. 4. Update the WPML plugins to the latest version and run the troubleshooting steps as described on the errata page.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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: You were able to translate the Global Header/Footer built with the Divi Theme Builder, but the custom header/footer was not displaying on the front end in the secondary language. Solution: We found two configuration issues causing the problem: 1. The translated Global Header was saved as a draft. We changed the setting under WPML → Settings → Translated documents options to 'Publish the translated post when original is also published' (default). We then published the translated Global Header. 2. Some Divi custom post types had incorrect translation settings. We set the post types 'et_theme_builder' and 'et_template' to 'Not translatable' under WPML → Settings → Post Types Translation. After these adjustments, the translated Global Header and Footer should now display correctly on the translated homepage.
If this solution does not resolve your issue or seems outdated, we 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 the problem persists, please open a new support ticket.
Problem: You are experiencing an Error 500 when sending content for translation either to a translator or a translation service. Your hosting support confirmed that they are not blocking WPML scripts and URLs, and no relevant server error logs are visible. Solution: We recommend enabling WordPress debugging to identify the issue. Here are the steps you should follow: 1. Edit your
wp-config.php
file to enable debugging. Add the following lines before the comment /* That's all, stop editing! Happy publishing. */:
file located in the /wp-content directory for any WPML-related errors. 4. Copy and paste the full error message here for further analysis.
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: If you're experiencing an issue where the currency suffix is incorrect (e.g., showing 'Kr' instead of '€') despite the currency amount being correct for your multicurrency setup in WooCommerce, this might be due to a configuration issue with the WooPayments plugin. Solution: We recommend checking the following settings in your WooCommerce: 1. Navigate to WooCommerce → Settings → WooPayments. 2. Try disabling the 'Enable Multi-Currency' option to see if this resolves the issue. If the problem persists, it could be related to incomplete configuration of the WooPayments plugin. In such cases, we suggest temporarily deactivating the WooPayments plugin to verify if this resolves the display issue.
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 continues, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
