Problem: If you're experiencing issues with product listings showing a grey box on the second page of results in a secondary language (Dutch) on your website, even after clearing server and WPML caches, we have identified a solution. Solution: We recommend editing the product in the original (English) language and simply clicking on 'Update'. This action can be performed in bulk on the product listings page to address the issue for all affected products. Please try this on your staging site first to confirm that it resolves 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. Should the problem persist, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client is experiencing issues with locked fields in WPML and has concerns about the translation of the footer, which does not display correctly across different language versions of the site. Solution: We clarified that the locked fields can be unlocked simply by clicking on the 'lock' icon. Regarding the footer, it appears that the client had previously attempted to fix the issue by deleting the translated footer template directly from the database. However, this did not resolve the problem as the footer still does not appear correctly. We suggested that the footer's translation issue might be due to the limitations described in the WPML errata for the Pro theme, where layout texts are not translatable via the WPML Translation Editor (https://wpml.org/errata/pro-theme-layout-texts-not-translatable-via-wpml-translation-editor/). The client can either manually translate the template or apply custom code to make it compatible with String Translation. We asked the client to confirm if they intend to use String Translation for the footer in the same way as the “Object (CPT) – Single View” template.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues (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: You are trying to transfer your WPML account and its subscription renewal to your client after upgrading to the multilingual CMS option, but found that the renewal transfer is no longer available. Solution: Unfortunately, it is no longer possible to transfer the renewal link to your clients. If your client wishes to manage their own WPML subscription, they will need to purchase a new subscription and re-register their site.
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 WPML Support Forum.
and similar for other language directories, it might be due to third-party plugins calling the
flush_rewrite_rules(true)
function excessively. Solution: We recommend trying the following steps: 1. Back up your site for safety. 2. Insert the following code into the functions.php file of your theme:
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: 1. When properties are duplicated on your website, they do not display the same main selected image for each language on the front end. 2. When properties are translated with WPML, the system shows doubled options in the backend, such as two descriptions and two sets of fields for each property in the translated versions. Solution: To address these issues: 1. Install the ACF Multilingual add-on to ensure compatibility between ACF and WPML. You can find the add-on and setup instructions here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/ 2. Increase your WordPress memory limit as it is below the minimum requirement. Add the following lines to your
Afterwards, verify the new memory limit under WPML > Support > WordPress > Memory limit.
If this solution does not resolve your issue or seems irrelevant, 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 reported that their stock is reduced multiple times when an order is processed, observing multiple stock reduction messages in both the original and translated languages. Despite using troubleshooting tools and clearing caches, the issue persisted. Solution: We suggested the client to: 1. Temporarily disable all WPML plugins. 2. Place a new order using the same product as in the problematic order. 3. Check if the same stock reduction issue occurs. This test will help determine if the issue is related to WPML or another factor. If the problem persists even with WPML disabled, it confirms that WPML is not causing the issue. We also recommended testing with only WPML, WooCommerce Multilingual (WCML), and WooCommerce activated, while all other plugins are temporarily disabled, to rule out conflicts with third-party plugins.
The client found that the issue was caused by too many webhooks configured in the payment gateway.
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, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket.
Problem: If you're experiencing issues where the original colors of elements are replaced with different colors after translating your website using WPML, this might be due to the theme's custom elements not being registered correctly for translation. Solution: We recommend adding the following CSS code in the Appearance -> Additional CSS section to fix the color of the specific element:
Additionally, to prevent this issue in the future, ensure that the theme authors register their custom elements for translation by following the steps described in our documentation: Registering Custom Elementor Widgets for Translation.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: When switching to English, all texts remain in German, and the header is not visible. Solution: If you're experiencing issues with texts not translating and headers disappearing when switching languages, it's likely due to unregistered Elementor widgets. We recommend registering your custom Elementor widgets for translation. You can learn how to do this by following our guide on registering page builder widgets.
We have registered the elements in your header and footer, and they should now appear correctly translated. If you encounter untranslated content on other posts or pages, you should contact the theme authors to ensure they register the custom elements they created. You can refer them to the same guide.
Additionally, you can add the necessary XML code for registration in WPML -> Settings -> Custom XML Configuration tab as outlined in the guide.
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.
Problem: When you click on a category in the dropdown menu, it redirects to a secondary language, such as from English to French. Solution: We recommend first clearing both your browser cache and server cache to ensure no old data is causing the issue. Additionally, if you are using any redirection or code snippet plugins, we suggest disabling them temporarily to test if they are affecting the behavior of the dropdown menu.
If the issue persists and the solution provided here becomes irrelevant due to updates or it does not apply to your case, please visit our support forum to open a new 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.
Problem: If you're experiencing issues where a QueryLoop does not display subpages in Spanish on your translated page, despite having the 'Set page parent for translation according to page parent of the original language' setting enabled, you are not alone. Solution: We recommend starting by closely examining the QueryLoop’s language/context resolution within the Site Pattern—especially how it detects and queries translated children in non-default languages. You should also investigate any WPML compatibility issues with full-site editing patterns and QueryLoop blocks. It's crucial to ensure that all page and pattern-level translation links and caches are validated. Avoid reiterating basic sync/edit/cache-clear steps; instead, review block output, site pattern translation integrity, and theme/block compatibility in the Spanish context. If necessary, collect a copy of relevant pattern and post data. 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 unable to translate using the automatic translation feature, it might be due to a temporary server overload or connectivity issues with our Advanced Translation Editor. Solution: We recommend trying the translation process again as the servers are now back to normal operation and the connectivity issues have been resolved. If you're still facing issues, it might be because the solution is 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 for further assistance.
Problem: Every time the client updates their contact page, the link to the desired language in Contact Form 7 is lost. The client tried using a previously suggested solution involving form ID translation, but could not find the contact form ID translation ID. Attempts to re-translate the contact forms and page were also unsuccessful. Solution: We recommend identifying the form ID as a first step. Once you have the form ID, you can apply the fix suggested in the WPML forum. If you're experiencing difficulties finding the form ID or the issue persists after applying the fix, please check our related known issues at https://wpml.org/known-issues/ and ensure you have the latest versions of themes and plugins installed. If the problem continues, we highly recommend opening a new support ticket for personalized assistance. You can do so here: WPML Support Forum.
Problem: The client is experiencing two issues with the localization of custom fields using WPML and ACF (Advanced Custom Fields): 1. A custom field is displayed with a lock icon and is set to translate, but it does not appear in the Advanced Translation Editor. 2. An ACF field that includes a document from the media library is not visible in the list.
Solution: We first clarified whether the ACF plugin was installed since only the Advanced Custom Fields Multilingual bridge plugin was visible. It's essential to have both the ACF plugin and the bridge plugin installed for proper functionality. We recommended checking the installation of the ACF plugin at https://www.advancedcustomfields.com/ and also suggested reading our guide on translating sites built with ACF at https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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 noticed that two payments were debited from their accounts without one being refunded and requested a refund for one of the payments. Solution: If you're experiencing a similar issue with billing or need a refund, we recommend contacting our admin team directly. Please use the following form to reach out for assistance: https://wpml.org/home/contact-us/contact-form/ For any technical issues on your site, feel free to contact us.
If this solution is not relevant 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client was unable to use the Advanced Translation Editor (ATE) as it was not loading and displayed an error 503. Solution: The issue resolved itself without any intervention from the client. If you're experiencing this issue, we recommend waiting a short period to see if it resolves on its own. However, if the problem persists, please check our related known issues and ensure you have the latest versions of themes and plugins installed. If none of these steps work, we highly recommend opening a new support ticket.
This solution might be irrelevant if it's outdated or not applicable to your case. If you need further assistance, please visit our support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
