Problem: The client reported an issue with the language switcher on a paginated taxonomy page. When switching from English to Chinese on page 4, the URL constructed loses the page suffix and language parameter, causing the page to revert to the default English page instead of the intended Chinese page 4. Solution: We identified that the issue was due to the incorrect order of URL parameters in the custom language-switcher filter. The solution involves modifying the filter to correctly assemble the page segment and the language parameter in the URL. Here is the corrected code:
This code ensures that the pagination segment is correctly placed in the URL, maintaining the intended language switch functionality. If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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.
Problem: When the WPML core plugin is active, all front-end content is squeezed inside a 325px-wide side-header container instead of appearing next to it. Deactivating WPML core alone resolves the layout issue, indicating that no other plugins or settings are causing this. The issue involves missing closing div tags in the server-rendered HTML output when WPML is enabled, affecting the global header (Full Page Section container).
Solution: We recommend the following steps to diagnose and potentially resolve the issue: 1. On a staging copy of your site, navigate to Appearance -> Themes and temporarily activate the Avada parent theme, keeping WPML Multilingual CMS, Avada Builder, and Avada Core active. 2. Open the homepage in a private browser window with WPML still active and check if the layout issue persists. 3. If the issue is resolved with the parent theme, it suggests that customizations in the Avada Child theme might be contributing to the problem.
Please note that this solution might become irrelevant due to updates or specific configurations that differ from your 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that translation jobs targeted at Luxembourgish in the Advanced Translation Editor were incorrectly showing German as the target language, with German content pre-filled. This issue was also evident in the PTC 'Improve Translations' suggestions panel, where Luxembourgish URLs were tagged with the German flag. Solution: We recommended the client to make a minor change to the default language page title and save it, then attempt to translate to Luxembourgish again to see if the issue persists. If the problem continued, we advised the client to provide regular admin access for further investigation. The client later reported that the situation had stabilized and no major translation issues were occurring.
Please note that this solution might be outdated or not applicable to your specific case. If you're experiencing similar issues, 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 the problem persists, please open a new support ticket.
Problem: The client was consistently receiving a warning on all admin pages stating that 'WPML is missing some records in the languages tables and it cannot fully work until this issue is fixed.' The 'Clear language information and repopulate languages' button, which is typically used to resolve such issues, was missing from the Troubleshooting page. Attempts to hard-refresh the page, update WPML, and run 'Set language information' did not resolve the issue. Additionally, there were stuck translation jobs and no relevant database errors found in the WP_DEBUG_LOG.
Solution: We reviewed the client's database directly for inconsistencies in 'icl_languages' and related WPML tables. After confirming that there were no relevant errors in the WP_DEBUG_LOG and that the issue was not due to a hard database/SQL error, we proceeded with a site-level review with temporary access. This allowed us to inspect non-surfaceable issues with language records and the missing repair button logic. The issue was resolved by fixing the database directly.
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 here.
Problem: After installing the WPML Media Translation plugin, the client encounters a persistent message stating, "The WPML Media Translation setup is almost complete. Click here to finish the setup." However, clicking the link leads to a loop without completing the setup. Solution: We have identified this message as a false warning. Our developers are aware and currently working to resolve it. You can safely ignore this message and continue using the plugin as normal without any issues.
If this solution does not apply to your situation, or if it becomes outdated, we 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. Should you need further assistance, please open a new support ticket.
Problem: If you're experiencing an error when switching languages on your WordPress site using the WPML plugin, where clicking on a different language (e.g., Thai/Russian) displays a page error instead of the translated content, this might be due to a known issue. Solution: We recommend applying a workaround described in the following erratum: https://wpml.org/errata/flux-checkout-fatal-error-uncaught-valueerror-unknown-format-specifier-t/. Before applying the workaround, ensure you have a full backup of your site and database. After applying it, check if the fatal error is resolved.
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 issue persists, please open a new support ticket at WPML support forum for further assistance.
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: If you're experiencing an issue where completed translations in WPML Advanced Translation Editor remain stuck as 'In progress' and are not imported back into WordPress, even after reactivating and registering the WPML license, clearing caches, and adjusting memory limits, the problem might be related to incorrect language settings. Solution: We recommend checking the language settings in WPML. Specifically, go to WPML > Languages > Edit Languages and ensure that the language is mapped correctly. For instance, if a translation job is set to a different language variant (like Swiss German instead of German), correcting this mapping and resending the job can resolve the issue. Please verify if this adjustment fixes the problem.
If this solution does not apply because it's outdated or not relevant 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported an issue where a menu created in Portuguese and translated into Spanish using WPML became duplicated in the default language. Additionally, the Spanish translation became unavailable, and the pencil icon to access the translation did not show the expected content. Solution: We acknowledged that this behavior is unexpected and suggested that something might have affected the menu or its translation relationship. We recommended checking the errata page for known issues related to menu translations at https://wpml.org/errata/menu-translations-losing-connection-and-displaying-as-duplicates-intermittently/. To further investigate and resolve the issue, we requested temporary access (WP Admin and FTP) to the client's site, preferably to a staging/test site where the problem has been reproduced. We informed the client that the connection would be made from Ukraine.
Please note that the solution provided 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 website is in English, but the automatic translation into Thai and Chinese doesn't work. Refreshing the English page does not update the translations; instead, an old version is displayed, and the “in progress” icons keep spinning. Solution: We recommend increasing the PHP memory limit to
If your hosting provider has a server-level PHP memory limit, you may also need to increase it from your hosting control panel or contact your hosting provider for assistance. After increasing the memory limit, try to reproduce the issue. Additionally, try disabling the option to translate everything automatically once to see if that resolves the issue.
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 at WPML support forum.
Problem: On the Malay homepage, clicking on the GX2002 product (both the image and the title) redirects to the Indonesian version of the product page instead of staying in Malay. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Edit the homepage in the original language. 2. Make a small change to the page title, for example, and update the page. Then, revert the change and update the page again. This may be necessary to trigger a new translation job, as the translation is currently marked as completed. 3. Open the Malay translation and update the GX2002 product link to the correct URL:
4. Complete the translation and save the changes. After completing these steps, the GX2002 link on the Malay homepage should correctly point to the Malay product URL.
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.
Problem: If you're experiencing issues with the translation of Yoast SEO metadata for WooCommerce products using WPML, where the Meta Description is not transferred or translated into the English version, while the Focus Keyphrase is correctly translated, this summary might help. Solution: We recommend following these steps based on the origin of the meta description: 1. If the meta description is from the default/fallback configured in Yoast SEO, translate it using WPML → String Translation. 2. If the product has a custom meta description, translate it through the Advanced Translation Editor (ATE). 3. If you manually edit the translated product using the WordPress editor, be aware that the manually entered meta description will override the translation created through ATE. For a detailed explanation, you can watch this video provided by our support team: https://www.loom.com/share/3a05de245c384f9d840cbd875e36d05e
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 our support forum.
Problem: The "Browse" button on the second slide of the homepage banner redirects to the English version of the page in all other languages (German, Spanish, Hungarian, etc.), instead of staying in the current language. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Edit the homepage in the original language. 2. Make a small change to the page title, for example, and update the page. Then, revert the change and update the page again. This may be necessary to trigger a new translation job, as the translation status is currently marked as completed. 3. Open each translation and add the correct link to the BROWSE button. 4. Complete the translation and save the changes.
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.
preg_match(): Argument #2 ($subject) must be of type string, array given
in the ACFML plugin while using ATE for translations. The error was due to attempting to translate forms created the 'old' way, resulting in empty translations when using ATE. Solution: 1. Increase the WordPress memory limit to at least 256MB by adding the following code to the
Place it above the line that says /* That's all, stop editing! Happy blogging. */. 2. Confirm that the WordPress memory limit adjustment is correct in WPML -> Support. 3. If you're experiencing similar issues, ensure you have created a full site backup that can be restored if necessary.
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.
Problem: The postcard in the original language has a selection of specific category posts that will be shown. The translated page does not keep this setting of specific categories, as it shows all kinds of posts also from categories not listed. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML > Settings > Custom XML Configuration. 2. Add the following XML configuration:
3. Save the XML configuration. 4. Make a small change to the original page and save/update it. 5. Update and complete the translation again. This updated configuration handles the relevant
include_*
and
exclude_*
taxonomy attributes more generally instead of defining each taxonomy individually.
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. Additionally, please feel free to open a new support ticket 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