Problem: If you're experiencing an issue where hovering over the flag in the WPML language switcher displays HTML code instead of the expected tooltip or language name, this might be due to how the theme handles HTML in menu items. Solution: 1. **Check Language Switcher Options**: Review your language switcher settings in WPML to ensure no HTML code is entered in fields meant for plain text. Navigate to WPML → Languages and check the 'Language switcher options' and 'Edit Languages' sections. 2. **Clear Caches**: If you're using a caching plugin or have server-side caching, clear these to ensure they're not causing the issue. 3. **Increase WP Memory Limit**: Increase your WordPress memory limit to at least 128MB by adding
define('WP_MEMORY_LIMIT', '256M');
in your
wp-config.php
file. 4. **Contact Theme Developers**: The issue might stem from how your theme's menu walker handles HTML. Contact your theme developers for a fix or try modifying the
start_el()
method in your theme's menu walker file to strip HTML tags from titles. 5. **Workaround**: As a temporary solution, you can add the following code to your child theme's
functions.php
to remove the title attribute for WPML switcher items:
If these steps do not resolve your issue or if the solution seems outdated or irrelevant 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.
Problem: The client is experiencing an issue where an unwanted language code prefix (e.g., 'DE', 'FR') is automatically added before the 'FREE SHIPPING OVER' text in the announcement bar on non-English pages of their multilingual website. The English version displays correctly without any prefix. Solution: 1. We recommended inspecting the Elementor templates by navigating to Templates → Theme Builder/Saved Templates to locate and edit the announcement bar widget. 2. Check the widget’s 'Advanced' settings, specifically the 'Before'/'After' fields, for any dynamic tags or shortcodes that might be adding the language codes, and remove any found prefixes. 3. Update the template after making these changes. 4. Search for related strings in WPML → String Translation and make necessary edits if the prefix is present in the translations. 5. If dynamic tags or custom PHP hooks in the child theme are conditionally generating the prefix, these should be reviewed and adjusted as needed.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: Клиент обеспокоен возможной несовместимостью WPML с темой ClassiAds и хочет убедиться, что WPML будет корректно работать с этой темой, включая перевод пользовательских полей, таксономий, виджетов Elementor, категорий объявлений, внутренних элементов темы и URL-структуры. Solution: Мы проверили наши записи и обнаружили, что тема ClassiAds не проходила официальное тестирование на совместимость с WPML. Это не означает, что она не будет работать, но мы не можем гарантировать корректную работу всех функций. Рекомендуем выбирать темы из списка официально протестированных и подтверждённых на совместимость: https://wpml.org/theme/ Также можно выполнить поиск в интернете по запросу "WPML + [название темы]", чтобы узнать о совместимости. Например, другие продукты того же автора, такие как Classified Listing Pro и Classified Listing Multilingual, были протестированы и подтверждены как совместимые:
Если данное решение окажется неактуальным или не подходит под ваш случай, рекомендуем открыть новый тикет поддержки. Также настоятельно рекомендуем проверить связанные известные проблемы https://wpml.org/known-issues/, убедиться в версии постоянного исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
Gestartet von: Anonymin: English Support
Schnelllösung verfügbar
Problem: The client reported issues with the language switcher on their website, where they often had to click twice on the French (FR) icon for it to switch languages, and sometimes it would revert back to English (EN) when navigating to another page. Solution: We recommended enabling the footer language switcher as a potential solution to improve the responsiveness and accuracy of language switching. Detailed guidance on setting up the language switcher can be found here: Language Switcher Options. Additionally, we suggested testing the language switcher functionality in different browsers to determine if the issue might be browser-related.
If this solution does not resolve the 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. Should further assistance be needed, please open a new support ticket at WPML Support Forum.
Problem:
When saving Automatic Translation settings in WPML (and other plugin settings like Hostinger Tools), client received a "Some error occurred" message. The settings were not being saved.
Solution:
During the investigation, I found that .htaccess file contained a custom "Trailing Slash Redirect" rule that was interfering with WordPress REST API requests.
This rule was forcing all URLs to end with a trailing slash (/), which caused:
- REST API POST requests (e.g., /wp-json/wpml/v1/save-automatic-translation-settings) to be redirected with a 301 status to the same URL with a trailing slash
- The browser converted the POST request to a GET request during the redirect (standard HTTP behavior)
- The REST API endpoint returned a 404 error because it doesn't accept GET requests at that URL
This affected all plugins using the WordPress REST API, not just WPML.
I modified the existing trailing slash redirect rule in .htaccess file to exclude REST API paths (/wp-json/).
Problema: El cliente no puede recordar su contraseña para proporcionársela a un desarrollador que necesita instalar WPML en un nuevo sitio. Además, el cliente intentó restablecer la contraseña, pero no recibió ningún correo electrónico de restablecimiento. Solución: Primero, recomendamos verificar la carpeta de SPAM para asegurarse de que el correo electrónico de restablecimiento no haya sido filtrado accidentalmente. Si esto no resuelve el problema, una alternativa es instalar el plugin instalador de WPML directamente. De esta manera, no es necesario proporcionar la contraseña al desarrollador, ya que no la necesitará para la instalación.
Si esta solución no es relevante porque está desactualizada o no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. También recomendamos revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, puedes visitar nuestro foro de soporte.
Problem: The client is experiencing an issue where two subscriptions are created when a customer purchases a product bundle consisting only of a service charge, instead of just one. This happens when WPML is enabled, and the issue does not occur in the default language (Norwegian) but appears in other languages. Solution: We identified that the 'Smart Coupons for WooCommerce Coupons' plugin might be causing the issue as it has not been tested for compatibility with WPML. We recommend reaching out to the plugin's developers to confirm its compatibility with WPML. Alternatively, consider using the Advanced Coupons for WooCommerce plugin, which is fully compatible with WPML and might suit your needs.
If this solution does not resolve your issue or seems irrelevant due to being 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.
Gestartet von: Anonymin: English Support
Schnelllösung verfügbar
Problem: The client reported that WPML was not fully installed on their second website, which was necessary for testing the carousel Media Translate feature. Solution: We checked the installation status and updated it accordingly. After the update, we confirmed that the issue was related to a validation problem, which we resolved. If you're experiencing similar issues, we recommend verifying that WPML is fully installed and functioning correctly on your site.
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 for further assistance.
Problem: The client is experiencing an issue where attempting to validate the Litespeed extension with QUIC.cloud results in a 404 error page when WPML is activated. This problem persists even after resaving permalinks with WPML deactivated, indicating a potential redirect issue caused by WPML. Solution: We recommend the following steps to troubleshoot and potentially resolve the issue: 1. Deactivate WPML and connect to the Litespeed Cloud. If successful, reactivate WPML and check if the issue reoccurs. 2. If the problem persists, create a sandbox site with a fresh WordPress, WPML, and Litespeed installation to verify if the issue is specific to the client's current site setup. 3. Consult with the hosting providers to check for any server-side configurations, firewall rules, or security directives that might be causing the redirect issue. Additionally, reviewing server logs may provide further insights into the problem.
If these steps do not resolve the issue or if the solution 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 for further assistance.
Problem: If you're experiencing issues with the width of the dropdown menu in WPML not being able to be shortened after adding CSS to WPML's additional CSS section, it might be due to the CSS settings of the JetMenu submenu. Solution: First, check the CSS controlling the submenu's width. The relevant CSS is:
property to a value that suits your needs. If you want to specifically target only the WPML menu item, use its unique ID, which in this case is
jet-mega-menu-item-wpml-ls-52-en
. Additionally, we recommend inserting the CSS in the WordPress Customizer under Appearance > Customizer > Additional CSS to ensure it takes effect.
If these steps do not resolve your issue, or if the solution becomes outdated, please check the related known issues and verify you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket on the WPML support forum.
