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.
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.
Problem: The client is encountering numerous 'Deprecated' error notices across various WPML files when using a recent PHP version (likely 8.1 or higher). These notices indicate that certain PHP functions need updating to comply with newer PHP standards.
Solution: 1. We recommend updating all WPML components to their latest versions via the Plugins > Commercial tab. 2. To hide deprecated and warning notices, adjust the
WP_DEBUG_DISPLAY
and related constants in your
wp-config.php
file. 3. Understand that these PHP deprecation notices do not impact your site's functionality and can be safely hidden in a production environment. 4. For an official update or timeline on when all deprecated code will be addressed, only a WPML specialist can provide this information. We do not have a specific timeline or roadmap available currently. 5. Check your PHP version through WordPress Site Health to ensure compatibility.
If this solution does not resolve your issue or seems outdated, please visit our known issues page and confirm you have the latest versions of themes and plugins installed. If needed, do not hesitate to open a new support ticket for further assistance.
Problema: El cliente no puede cambiar el slug del idioma portugués de 'pt-pt' a 'pt' en su sitio multilingüe WPML. Solución: Si estás experimentando este problema, te recomendamos seguir estos pasos: 1. Crea un nuevo idioma personalizado en WPML con el código 'pt'. 2. Duplica todo el contenido del idioma 'pt-pt' al nuevo idioma 'pt'. 3. Elimina el idioma antiguo 'pt-pt' para evitar conflictos. Para más detalles sobre cómo realizar estos pasos, por favor consulta nuestra documentación aquí: https://wpml.org/forums/topic/how-to-change-language-url-format-code/
Si esta solución no resuelve tu problema o si la información parece desactualizada o no aplicable a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Si necesitas asistencia directa, por favor visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: The client was experiencing issues with WPML not functioning correctly due to the WordPress REST API not responding as expected. Additionally, there was a compatibility issue with the Breakdance plugin, which was not working with WPML. Solution: 1. We recommended checking if any security or firewall plugins were blocking REST API requests, or if the REST API had been disabled via the rest_enabled filter. 2. We suggested ensuring that server configurations or custom rewrite rules were not interfering with WordPress routing. 3. We advised the client to flush any existing cache memory that might be causing issues. 4. We increased the WordPress memory limit by adding the following code to the wp-config.php file:
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. Please do not hesitate to open a new support ticket for further assistance.
