Problem: A single bundled product disappears on the homepage when viewed on a mobile device, although it displays correctly on desktop. Solution: If you're experiencing this issue, we recommend first checking if the problem persists when WPML is temporarily disabled. This step helps determine if WPML is contributing to the issue. Additionally, we have enabled debug information for this support ticket to further investigate 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 at WPML support forum for further assistance.
Problem: Wenn Sie zu WPML → Übersetzungen gehen und versuchen, eine Übersetzung zu übernehmen, erhalten Sie eine Fehlermeldung: 'Authentifizierungsfehler, bitte kontaktieren Sie Ihren Übersetzungsmanager, um Ihr Abonnement zu überprüfen.' Dies tritt auf, wenn das Plugin 'Add Admin CSS' aktiviert ist. Solution: Wir empfehlen Ihnen, das Plugin 'Add Admin CSS' zu deaktivieren, da es nicht mit WPML kompatibel ist und Konflikte verursacht. Dadurch sollte WPML problemlos funktionieren.
Falls diese Lösung 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 verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.
Problem: You are setting up WPML on your website and have encountered an issue with the automatic translation review process. Some translations are marked as “Needs Review.” When you click on “Review,” you cannot see the content properly; you only see the full text when you choose to edit it. You are concerned about accidentally publishing these translations because you are not sure if you can easily revert them afterward. You want to review and confirm translations without publishing them live yet. Solution: The issue you are experiencing is due to the incompatibility between YOOtheme and WPML. Although the content was translated by WPML, YOOtheme still shows the untranslated content in secondary languages. To manage this, we recommend using the WordPress Editor to create translations. This approach ensures that you see the translated content when reviewing. For more details on how to use different translation editors, please visit Using Different Translation Editors for Different Pages.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with the Houzez theme where invoices are not being generated when an order is marked as 'Completed' in a multilingual environment using WooCommerce and WPML Multilingual CMS is active, this might be due to WPML settings. Solution: We recommend setting the Invoice post type to not be translatable, similar to the refunds and orders post types. This adjustment should resolve the issue, allowing invoices to appear correctly after the order is completed. Please verify this solution on your staging site and confirm its effectiveness.
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 at WPML support forum for further assistance.
Problem: If you're experiencing issues with photos not displaying on translated pages, it might be due to how custom fields are synchronized. In this specific case, the custom fields managed under a custom taxonomy do not synchronize properly, leading to empty images in translated listings. Solution: We recommend checking if the custom fields are set to 'not translatable' and re-saving the related content. However, if these steps do not resolve the issue, it's likely because the plugin managing these fields is not officially compatible with WPML. We suggest contacting the plugin authors to discuss this behavior and inquire about potential compatibility or updates. You can find more information about known issues and compatibility on the WPML Known Issues page.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We highly recommend verifying that you have installed the latest versions of themes and plugins. For further assistance, visit our support forum.
Problem: The client was experiencing a 'Page not found' error when accessing WPML → Media Translation, preventing media synchronization. Additionally, the site logo was missing on translated English pages in an Elementor Header template. Solution: 1. We identified that the issue was caused by the WP Admin UI Customize plugin, which is not compatible with WPML. We recommended deactivating this plugin. 2. After deactivating the plugin, we instructed the client to clear both Elementor and browser caches. 3. We then manually synchronized the logo file in WPML's Media Translation by ensuring the same file was used for both the default and English languages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket here.
Problem: If you're experiencing a 500 internal server error when accessing WordPress REST API endpoints like wp-json/wp/v2/posts with the default language parameter (?lang=ar) in a multilingual site using WPML, the issue might be due to incorrect string translations. Solution: We recommend checking the translation of specific strings in the WPML String Translation. For instance, the problematic string could be:
Delete the user's %1$s and %2$s data when the %3$s access expires.
Ensure its translation is accurate. In this case, the correct translation should be:
احذف بيانات المستخدم %1$sو %2$s عند انتهاء صلاحية الوصول %3$s.
After correcting the translation, verify that the endpoint no longer returns a 500 error.
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 for further assistance.
Problem: The client is using radio option values that aren't translatable in their project. Solution: We recommend setting up the radio options to be translatable by following the method described on the Advanced Custom Fields site. Specifically, format the choices field like this:
red : Red
. After updating the choices, the client should try translating the labels as explained in the WPML documentation on translating sites built with ACF. For more details, visit the following links:
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 open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with the Divi Flash Table not displaying hyperlinks correctly in secondary languages on your website, such as showing HTML code instead of functioning links. Solution: We recommend updating your XML configuration for the Divi Flash Table. Replace your current XML configuration with the following code:
After updating the XML configuration, refresh your page and update the translation. This should resolve the issue and display the links correctly.
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.
Problem: The client is experiencing issues with the translation of Next Bricks elements on their website using WPML. The default language is Croatian, and when switching to English, most of the content remains in Croatian. Additionally, there are issues with translating ACF option page content.
Solution: For the Next Bricks translation issue, we recommend the following steps: 1. Navigate to the
For the ACF option page content translation issue, follow these steps: 1. Open the Field Group for the option page and set the translation preference to "Same fields across languages." 2. Go to "Option Pages" from the dashboard. 3. Switch to English using the language switcher in the admin top bar. 4. Add content in the Email and Telephone fields.
This should resolve the translation issues. If these solutions do not work or become outdated, or if they do not apply 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.
