Problem: If you're experiencing issues where text blocks appear as single units on your webpage and UI builder but are incorrectly split into fragments when opened for translation in Crowdin, causing loss of context for translators, this might be due to line breaks in the Text Block Element of WP Bakery Page Builder. Solution: We recommend adding the following code to the
functions.php
file of your theme to prevent automatic addition of paragraph tags which might be causing this issue:
After adding this code, please modify the page content or add new content and test the changes. If the problem persists, it might be due to inherent behavior of the WP Bakery Page Builder in conjunction with Crowdin, and changes in the source text might be necessary to resolve the 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 open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that some ACF Field Groups were duplicated when new languages were added to their site. They inquired whether it was safe to delete these duplicates and how to prevent such duplication in future projects. Solution: We identified that the duplication occurred because the ACF Field Groups were set as translatable in the WPML settings. To resolve this, we advised the client to set the ACF Field Groups to 'Not Translatable' in the WordPress Dashboard under WPML > Settings > Post Type Translation. This change prevents future duplications by ensuring that field groups do not create copies when new languages are added. The client should safely remove any existing duplicates, as they are no longer necessary.
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: You are experiencing issues with your website translations and encountering errors. Solution: 1. Navigate to your Dashboard > Pages. 2. Open the edit screen of the original page and make a minor change, such as adding an extra blank space at the end of a sentence or paragraph. 3. Save the changes. A circular arrow should appear beside the second language links, indicating that an update is required. 4. Edit the translation again and ensure it is saved up to 100% translated. 5. If the issue persists, check the WordPress Dashboard > WPML > Translation Dashboard for a dialog box asking you to migrate the website. If present, complete the setup following the instructions at this link. 6. If no dialog box is present, unregister and re-register WPML: - Navigate to WordPress Dashboard > Plugins > Add New > Commercial (Tab). - Click the "Unregister WPML" link. - Click the "Register WPML" on the right section of the screen. - Follow the process to get a new site key and enter it. For more details on registration, visit this link. 7. If the problem still exists, navigate to WordPress Dashboard > WPML > Support > Advanced Translation Editor (Error Log) and report the error seen at the top row of the table.
If this solution does not resolve your issue, or if it 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: If you click on English, a popup template with an Elementor Pro loop grid widget appears. In the second and third columns on desktop, the custom CSS for the loop items is missing, although the items are translated. The popup items look correct in English but appear strange in other languages, with the editor showing white but visible in the Structure Panel. Solution: We have developed a small plugin to address this issue temporarily. Please back up your website first. Then, download and install the plugin from this link. After installation, make a minor change to the original page and ensure it is 100% translated. This should resolve the problem temporarily. Our development team is aware of the issue and is working on a more permanent solution.
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 set up a title bar image for each page using Avada layout section and defined the title and image location in Avada page options. After translating the first page, the title bar image did not appear on the translated page. Solution: 1. Navigate to WPML -> Settings and scroll to the Custom Field Translation section. 2. Search for fields starting with pyre_ or fusion_ (Avada's prefixes for Page Options). 3. For title bar background images and retina images, set them to Copy if the same image is desired across languages, or Translate if different images are needed per language. 4. Set heading and subheading text fields to Translate. 5. Click Save at the bottom of the page.
If this solution does not resolve your issue, or if it 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're trying to fix technical SEO issues like improper URLs and need these changes to propagate to different language versions of your site, you might encounter issues where changes do not always apply. This could be due to issues in the Media Translation add-on, specifically causing double slashes (//) in media links. Solution: First, ensure you have a backup of your site. Then, if you're comfortable with code changes, you can manually edit the file at
Save the changes. However, this is a temporary workaround. We have released WPML 4.9.3, which includes a permanent fix for this issue. You can download the new version from https://wpml.org/account/downloads/. After updating, you can remove the manual code edit.
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 issues persist, please open a new support ticket at WPML support forum.
Problem: If you're using BeTheme with WPML and notice that English posts display the excerpt correctly above the featured image, but German posts translated via WPML do not show the excerpt (the wrapper gets class no_content and is empty), even though the excerpt is saved correctly in the database. Solution: We recommend following these steps to resolve the issue: 1. Ensure that the BeTheme template is fully translated and synchronized. This was the root cause in a similar case. 2. Check the BeBuilder data storage settings and ensure they are set to 'Serialized', and that 'mfn-page-items' is set to 'Translate' in WPML Custom Fields. 3. Visit the documentation on making BeTheme content available for translation. If these steps do not resolve the issue, it 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: After migrating a site from a staging environment to production, the Advanced Translation Editor (ATE) cloud was rejecting all translation jobs with an HTTP 426 error, indicating a URL change. The client attempted various troubleshooting steps, including reactivating WPML plugins and confirming site key registration, but the issue persisted. Solution: We recommended the client to re-save the original pages in the default language (DE) to refresh the database entries. This action allowed the ATE to recognize the correct production URL and accept translation jobs. The client confirmed that after re-saving the affected pages and updating the translations, the issue was resolved.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: You receive a notification that a file within the folder wp-content/plugins/wpml-string-translation/lib/StringScanning/vendor/wp-cli/php-cli-tools/lib/cli/unicode/regex.php is identified as malware by the Malcure Malware Shield plugin. Solution: We have confirmed that this alert is a false positive. It will be addressed in a future WPML release, and the alert should no longer appear once the fix is included.
If this solution becomes irrelevant due to updates or if it does not resolve your issue, 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client reported that videos and images were not displaying correctly on the Danish version of their product pages compared to the English version on their WooCommerce site using the JetixWP plugin. Solution: We recommended the client to first update WPML and its addons to the latest versions by following these steps: 1. Create a backup of the website. 2. Navigate to WordPress Dashboard > Plugins > Add new > Commercial (tab). 3. Click the Check for Updates button and update WPML and its addons. For more information on automated updates, visit https://wpml.org/faq/install-wpml/#automated-updates. Next, ensure media translation settings are correctly configured: 1. Go to WordPress Dashboard > WPML > Settings > Media Translation. 2. Check all enabled checkboxes and click the Start button. 3. Wait for the process to finish. Then, make a minor edit to trigger an update: 1. Navigate to Dashboard > Products and open the edit screen of the original product. 2. Make a small change and save it. 3. Edit the translation again and ensure it is 100% translated. Additionally, we enabled the COPY option for specific custom fields related to video features, which 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. If the problem persists, please open a new support ticket at WPML support forum.
Problem: When translating a page, no content appears translated, and the translation editor shows zero words. Solution: The issue was traced to custom code in the child theme that was preventing WPML scripts from loading correctly. We recommend switching to the parent theme to verify if the translation editor then functions properly and the content becomes visible for translation. If the issue resolves, review and possibly disable parts of the custom code in the child theme to isolate the exact cause. If further assistance is needed, we suggest visiting our support forum.
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: The client reported that WPML has been displaying fields in the translation interface related to the 'spacer' element from Elementor, which was not initially present but appeared recently. Solution: We recommended the client to ensure that both their development and production environments are identical in terms of plugins, configurations, and server settings. We suggested performing monthly maintenance and updates to keep the system up-to-date. After the client performed these updates and forced a refresh of the WPML translation status on the affected pages, the issue was resolved. If you're experiencing this issue, we recommend ensuring your environments are consistent and performing regular updates. If the problem persists, consider refreshing the WPML translation status on the affected pages.
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 at WPML support forum.
Problem: The client is experiencing an issue with the mega menu not working correctly in the Azerbaijani language version of their website. The menu works fine in English, but shows errors when switched to Azerbaijani. The error message '404 (Not Found)' appears in the console when trying to edit the mega menu in the Azerbaijani version. Solution: We suggested checking for a plugin conflict by deactivating the Elementskit plugin, which is used for the mega menu, to see if the issue persists. This approach was recommended because a similar issue was resolved on another site by resetting the permalinks, but this did not work in the current case. If you're experiencing this issue, we recommend trying to deactivate the plugin temporarily to check if it resolves the problem.
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.
Problem: The client reported that several plugins were not functioning correctly on the English version of their website, and templates were not displaying properly in both English and Arabic. Specifically, when WPML was enabled, the homepage displayed a 'Page not found' error, but when WPML was disabled, the homepage loaded correctly in Arabic (the default language). Solution: We asked the client to describe the issue step-by-step and to increase the WordPress memory limit by adding the following to their wp-config.php file:
After reviewing the site's configuration and running some troubleshooting steps, we identified that the 'admin_texts_show_on_front' string was incorrectly translated in WPML's String Translation. We deleted this string and disabled the redirection, which resolved the homepage loading issue. We then applied the same solution to the production site.
If this solution does not resolve your issue, or if it 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 problems persist, please open a new support ticket at WPML support forum.
Problem: After updating WPML to the latest version, the client experienced an issue where the 'Translate content' button was disabled (greyed out) when editing products on a WooCommerce site. This problem affected all products and persisted despite running WPML troubleshooting tools, switching to the Classic Translation Editor, and testing multiple products. The issue was linked to the WPML REST API requests being blocked. Solution: The issue was resolved by identifying that custom security rules in the server configuration (.htaccess and WAF) were unintentionally blocking WPML REST API requests. With the assistance of the hosting provider, these rules were removed, restoring full functionality to the translation dashboard and bulk translation process.
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 https://wpml.org/forums/forum/english-support/.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
