Problem: The client's website, arnaudhomburger.fr, was redirecting to arnaudhomburger.com unexpectedly, affecting their Google Ads campaign. The issue temporarily resolved after clearing the WordPress cache but recurred shortly after. Solution: We recommended checking the
wp-config.php
file for dynamic URL configurations. Specifically, we advised replacing:
After making these changes, we suggested clearing both WordPress and server cache and checking the site in a private browser window to ensure the redirection issue was resolved.
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: The client is using WPML on their WordPress website and wants to enable the language switcher as a dropdown in the header built with Elementor, but is unsure how to set it up correctly. Solution: If you're using the language switcher added through WPML → Languages, you can customize it with several options, including how it's displayed. For more details on styling and display settings, visit WPML Language Switcher Options. If you're using the WPML Language Switcher widget in Elementor, check the widget settings for supported display modes. If the dropdown option is not available in the widget settings, it will not be possible to display the switcher as a dropdown.
Please note that this solution might be outdated or not applicable to your specific case. 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 issue persists, please open a new support ticket.
Problem: The client was unable to translate certain sections of their website, specifically the Service Categories in the Case Tab Scroll widget, which were pulling data from the Services custom post type. Solution: We discovered that the Service Categories taxonomy was set to 'Not translatable' in the WPML settings. To resolve this, we changed the setting for Service Categories (service-category) to:
Translatable – only show translated items
We also noticed that some categories still had names in Greek. We recommend the client to translate or rename these categories to ensure consistency across languages. For demonstration, we updated one category by adding 'EN' to its name. The client should review and update the remaining categories similarly.
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 issue persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
The customer could not see or translate all ACF field groups and fields for new languages. In expert mode, the fields were missing from the meta boxes and connecting to the original translation did not solve it.
Solution:
The ACF field groups had been set as translatable, which caused duplicate field groups and prevented the fields from working correctly in translation. The fix was to set acf-field-group to Not Translatable in WPML settings, delete the duplicated field groups, and then make a small update to the page so the fields appeared correctly in translation. The customer confirmed this resolved the issue.
Problem: The button in the info box of the Kadence theme is not translating. Solution: If you're experiencing this issue, we recommend you try the following steps:
1. Go to WPML → Settings → Custom XML Configuration.
2. Add the following configuration and click Save:
3. Edit the original page in the WordPress editor and make a small change, such as adding a character to the page title.
4. Save the page.
5. Open the translation and update it.
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 at WPML support forum.
The customer noticed that the WordPress admin was loading slowly and saw delayed requests to the WPML endpoint ams.wpml.org/mini_app/dashboard.js. They wanted to know whether this was caused by a WPML setting or a blocked endpoint.
Solution:
It was confirmed that the endpoint was reachable and the site was not blocked on WPML’s side. No WPML setting was identified that could cause this behavior. Since the issue later stopped on its own, it was treated as a temporary connectivity or whitelist-related issue outside of WPML. The customer was asked to monitor it and report back if it returned.
Problem: If you're experiencing an issue where ACF field labels such as 'Location' and 'Photographer' display in English instead of Hebrew when accessing a Hebrew post directly via a /he/ URL, despite having translated these labels in WPML String Translation, this might be due to the labels not applying when the language is determined solely from the URL path. Solution: We recommend updating your WPML plugins and all related add-ons to the latest version, currently 4.9.5, to ensure you have the latest bug fixes and improvements. You can check for updates in your WordPress dashboard under Plugins → Add New → Commercial, or download them from My Account → Downloads on wpml.org. Before updating, please make sure to back up your database. If updating does not resolve the issue, we may need temporary access to your site to investigate further.
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 problem persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where the translation job appears to be completed in WPML's Advanced Translation Editor (ATE), but when WPML tries to download/apply the translation, it fails. The error message indicates that the uploaded XLIFF file is not properly formed, specifically missing or having incorrect 'target' data. Solution: We recommend checking the character encoding settings in your WordPress configuration. Here are the steps to resolve the issue: 1. Open the
wp-config.php
file. 2. Replace the line:
define('DB_CHARSET', 'cp1251');
with:
define('DB_CHARSET', 'utf8mb4');
3. Save the changes and update the original page to check if the translations are saved correctly. Before making these changes, please ensure to create a full backup of your site and database.
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.
Problem: On translated pages, ACF WYSIWYG fields fail to load because the TinyMCE script is not being enqueued. This issue affects the Event post type generated by The Events Calendar plugin and does not occur on the original language pages.
Solution:
The issue appears to be related to the "Event Tickets" plugin.
If these steps do not resolve the issue, or if the solution seems 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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: The client reported issues with WPML on a WordPress site with Tutor LMS, where menus were incorrectly displaying in multiple languages, language switchers were disappearing or malfunctioning, and courses were being altered unexpectedly. Solution: We advised the client to focus on one issue at a time, starting with the menu problems. The steps included: 1. Deleting all unnecessary menus in the default language (English) and other languages. 2. Ensuring only the required menus are kept and then translating these menus using WPML. 3. Checking the front end to ensure that the menus display correctly after translation. We also suggested handling the Tutor LMS course issues in a separate ticket to keep the troubleshooting process clear and organized. If this solution does not apply to your situation, 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/.
Problem: The client reported that although ATE translation was complete and saved, the translated version of the page appeared in English except for the title. This issue was consistent across all languages for that specific page, despite the settings being correct. The content was added as a Classic block, and while the translation was correct in the ATE, it did not display correctly in the backend. Solution: We suggested checking how the page was built in the default language and whether it involved ACF fields, custom Gutenberg blocks, standard WordPress blocks, or a page builder. We also recommended manually editing the translated page directly to see if the content displayed correctly in the backend, which could indicate issues with frontend rendering rather than the translation itself. After gaining access to the site, we made a small change to the page in the default language, saved it, and re-translated it. This resolved the issue. We also deleted the existing translation package for that page, made a minor change to the title in the default language, saved the page, and then re-translated it. This approach helped synchronize the content correctly.
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 for further assistance.
Problem: If you're experiencing issues with syncing secondary cart bookings to Google Calendar while WCML is active in version 5.5.5, Solution: We recommend trying a workaround until the issue is addressed in WCML 6.0. You can find the workaround details here: WPML forum post.
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 at WPML support forum.
Problem: If you're experiencing issues with your mobile menu, such as repeated language options and incorrect font size or color, it might be due to having two language switchers configured in the menu. Solution: We recommend checking your mobile menu settings to ensure that only one language switcher is active. You can do this by reviewing the menu, theme, or builder settings where the language switchers were added. If you find two language switchers, consider removing or disabling one of them. Additionally, consider adding the custom CSS in WPML → Languages → Language Switcher Options to address the font size and color issues.
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 at WPML support forum.
Problem: The client was unable to see the place to paste the code for automatic translation because both the main site and the subsite did not have any credits available. Solution: We recommended the following steps to resolve the issue: - Unregister WPML from the site by going to Plugins → Add New Plugin, clicking on the Commercial tab, and then clicking the "Unregister WPML" button. - Delete the current sitekey from https://wpml.org/account/sites/ - Create a new sitekey - Register the site with the new sitekey using the same steps as unregistering the site. - Once registered, you will be able to see the allocated credits on the main site. - Login to the sub-site and create a migration code. - Connect with the main site. This process ensures that the sitekey is updated for proper credit and plugin management, and it will not affect the translations.
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 was experiencing an issue where the translated version of the 'Offers' page in English was generating incorrect URLs like '?offer_category=school-holiday' instead of normal translated page URLs. This was due to a conflict between the page slug and a taxonomy term. Solution: We resolved the issue by changing the slug of the English 'Offers' page from 'offers' to 'offers-page'. This adjustment corrected the URL structure and resolved the conflict with the taxonomy term.
If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
