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 do not hesitate to open a new support ticket or visit our support forum.
Problem: The client is experiencing an issue where translations appear correctly when the 'Look for strings while pages are rendered' option is enabled in WPML > String Translation, but appear differently when the option is disabled. Solution: We recommend the following steps to address the issue: Basics: - Add the textdomain in 'Localization options > Automatically load the theme's .mo file using 'load_textdomain'' under WPML > Theme and plugin localization. - Generate the MO file from WPML > Support > Troubleshooting > 'Show custom MO Files Pre-generation dialog box' option. - Ensure that the DB charset is configured under config.php to utf8mb4. - Go to WPML > Languages > Edit languages and re-save the settings. - Delete the strings completely, register them again, and retranslate. - Visit WPML > Support > troubleshooting and try all the suggested actions: https://prnt.sc/rqcSNCt3DVLY Advanced: - Check how these strings are called in your code and change the domain of the string. - Scan and re-translate strings via WPML String translation. - Check what the plugin uses to load the textdomain. These steps should help resolve the issue, which is likely related to incorrect code or a compatibility issue.
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 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, you can contact us directly at the WPML support forum.
Problem: The client reported an issue where footer widgets translated using string translation were still appearing in English on the frontend when French was active. Solution: We recommended creating separate widgets for each language to ensure that the translations display correctly on the frontend. This approach can be more reliable than using string translation alone for widgets. For detailed steps on how to set up different widgets for different languages, please visit Translating Widgets.
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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum.
Problem: The client reported that some text on their translated pages was not appearing as translated, despite being translated in the translation manager. This issue was not related to custom Gutenberg blocks but was occurring across various parts of the website. Solution: We recommended increasing the WP_MEMORY_LIMIT to at least 256M as the initial step, as low memory can prevent WPML from loading all elements properly. Instructions for increasing the site's memory limit can be found here: https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#how-to-increase-your-sites-memory-limit. After increasing the memory limit, the client was advised to re-save the translations by following these steps: 1- Open the concerned page/post in the default language 2- Add a small edit to it 3- This will reset the elements for WPML, and changes the status to "needs update" 4- Open the page with the translation editor and update the translation and hit complete 5- Delete WPML cache from WPML > Support > troubleshooting > Clear Cache in WPML.
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.
Problem: Sie haben festgestellt, dass in einem globalen Divi-Modul Texte automatisch aus einer anderen Sprache in die Elternsprache ersetzt wurden, ohne dass dies beabsichtigt war. Solution: Wenn Sie dieses Problem erleben, empfehlen wir Ihnen, alle Caches auf Ihrer Website zu leeren und das Modul erneut zu überprüfen. Es ist möglich, dass Cache-Einstellungen dieses unerwartete Verhalten verursachen.
Falls diese Lösung nicht relevant sein sollte, weil sie veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.
public static function iterate( $fields, $transformField, $transformLayout, $fieldBasePattern = '' ) {<br /> foreach ( $fields as &$field ) {
To:
public static function iterate( $fields, $transformField, $transformLayout, $fieldBasePattern = '' ) {<br /> foreach ( $fields as &$field ) {<br /> if ($field["value"] == NULL ){<br /> continue;<br /> }
NOTE: Always ensure you have a recent and working backup before making any changes.
Update
ACFML 2.2.0 (released February 2026) includes the permanent fix for this issue. You no longer need to manually apply patches after each plugin update. The plugin now skips unnecessary processing when field values are unchanged, significantly reducing the overhead on acf/load_field.
Problem: The client was unable to get automatic translations to work, as the process was stuck at 0%. Additionally, there was an issue with losing 400 credits after cancelling a previous job, and an error message on the jobs screen indicating that 'jobs could not be loaded'. Solution: We added 1000 credits back to the client's account to compensate for the lost credits during troubleshooting. For the automatic translation workflow, translations should run automatically, and then the client should review them at WPML > Translation before they get published, depending on the settings configured at WPML > Settings > Automatic Translations. If issues arise, the client can check the WPML > Support > ATE Error Log to diagnose problems. We advised the client to reach out again if further issues occur.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing issues with translating new page elements on your website using WPML. Despite deleting and creating a new translation, the new elements do not appear, and the old layout remains. Solution: 1. In ACF > Field Groups, delete all the groups you created in secondary languages and keep only the original one in your primary language. 2. In WPML > Settings > Post types translation, set Field Groups (acf-field-group) to "Don't translate". 3. Install the ACF Multilingual add-on using the banner at the top of your dashboard. 4. Go back to ACF > Field Groups, edit the original group (the only one left), and select the multilingual mode "Same fields across languages". This setting allows you to use the same group and translate the value of each field. For more information, visit https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/
It's important to note that in that particular case, the client was also experiencing an issue related to permalink manager.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client was trying to launch the French translation of their site.
Solution: Although the French version was no longer hidden and accessible directly via URL, it was not appearing in the language switcher. The client tried refreshing the cache and adjusting various settings, but initially, these actions did not resolve the issue. After adding a menu language switcher, both the custom and the menu switchers worked, but removing the menu switcher caused the custom switcher to revert to not showing the French option.
If this solution does not apply to your situation, 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 do not hesitate to open a new support ticket.
Problem: The client is experiencing an issue where the "Aplica acum" button in the Off-Canvas menu does not change when switching languages and does not redirect to the translated version of the link. Solution: First, we asked the client how they were translating the menu and verified that there was no translation for the Off-Canvas menu under WP-Admin -> Appearances -> Menu. We provided detailed instructions on how to translate menus, which can be found here: Translating Menus Documentation. After further investigation, we discovered that the issue was related to the synchronization settings in WPML -> Menus Sync. We ran the synchronization for the "Off-Canvas" menu, which resolved the issue, ensuring that the menus in Romanian synchronized correctly with the translated menus in English.
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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: You added a custom field "menu-title" to each menu and want to display this title above the menu with a shortcode, and you're wondering if it's possible to translate this value with string translation without translating the whole menu. Solution: We recommend creating the header and the custom field in the original language first. You can then translate them and use them normally. It's not mandatory to translate both the header and the custom field; if you prefer, you can create a custom field for each language separately. For more detailed guidance, please check our documentation on translating custom fields: Translating Custom Fields.
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 do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
Problem: The client wants to prevent the translation of the company name 'Routes' to 'Rutas' in different languages on their website. Solution: If you're experiencing this issue, we recommend you add the string 'Routes' to the glossary to prevent its translation. You can follow the steps described in our guide on how to create and manage glossary entries. Here is the link to the guide: How to Create and Manage Glossary Entries.
Please note that this 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 for further assistance.
Problem: The Blog Main page is not displaying translated post pages. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to Pages -> All Pages. 2. Edit the blog page. 3. Click on the update button. 4. Update the page's translation.
This approach should ensure that your Blog Main page displays the translated posts correctly. 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, please visit our support forum at WPML Support Forum.
Problem: The client is experiencing an issue where the WordPress menu element in a pop-up is showing twice in the English version, and the dropdown icons are very large. Solution: We recommended conducting a plugin conflict test by deactivating all plugins except for WPML, its addons, and Elementor to identify if the issue is caused by a plugin conflict. Additionally, there is a known issue with Elementor PRO popups that might be related. We advised checking the Errata page for more details and trying the workaround mentioned there: https://wpml.org/errata/elementor-pro-inline-css-not-rendered-for-translated-pop-ups/
If the problem persists, we recommend opening a new support ticket or using the chat support for immediate assistance at this link. We also highly 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.
Problem:
The client was facing Batch rolled back issues in sending jobs to translation services in few languages.
Solution:
The client said "The problem was settings at translation service "K&J Translations". Looks they didn't accept all languages i wanted to translate, so i got an error."
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
