Problema: El cliente está recibiendo un mensaje indicando que su sitio no cumple con los requisitos mínimos de WPML. Solución: 1. Verificar los límites de memoria del sitio: - Ir a Herramientas → Salud del sitio en el escritorio de WordPress. - Hacer clic en la pestaña Información. - Expandir las secciones Servidor y Constantes de WordPress. - Buscar el Límite de memoria de PHP y el Límite de memoria de WordPress. WPML requiere un mínimo de 128 MB para cada uno. - Si los valores son inferiores a 128 MB, contactar al proveedor de alojamiento web para aumentarlos o consultar guías en WordPress sobre cómo hacerlo. 2. Revisar la configuración de la API REST de WordPress: - Verificar si algún plugin de seguridad o configuración de firewall está bloqueando las solicitudes no autenticadas a la API REST, necesarias para el funcionamiento de WPML. - Desactivar o ajustar la configuración que restringe el acceso y borrar la caché del sitio. 3. Comparar los requisitos del sitio con los mínimos de WPML en https://wpml.org/home/minimum-requirements/.
Si después de seguir estos pasos el problema persiste o la información proporcionada aquí no es relevante debido a que podría estar desactualizada o no aplicar en 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. Para asistencia adicional, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: You are using WPML on your site and are trying to exclude certain elements from being removed by the 'Remove Unused CSS' feature in the WP Rocket plugin. You are experiencing issues on the front end with the second language when using this feature. Solution: We recommend contacting the WP Rocket support team directly for assistance with configuring their settings to work well with your site, as this issue involves a third-party plugin and falls outside our scope of support.
If this solution is outdated or does 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. Should you need further assistance, please open a new support ticket with us.
Problem: The client is using WPML to translate images for different languages on their website. Some translated images are not displaying correctly across various language versions of the site. Solution: We visited the page provided by the client and confirmed that the images are displaying correctly. If you're experiencing this issue, we recommend trying the following steps: 1. Clear your browser's cache. 2. Try accessing your site in incognito mode. 3. Use a different browser to see if the issue persists.
4. Sent the page to translate again.
If these steps do not resolve the issue, it might be because the solution is 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 continues, please open a new support ticket at our support forum.
Problem: The client is experiencing a PHP fatal memory exhaustion error when attempting to synchronize attributes and update product variations on a WooCommerce site with WPML active, even after increasing the server's memory to 768MB on a cloned site. Solution: We recommended performing standard conflict checks to isolate the cause, which involves: 1. Deactivating all non-essential plugins except for WPML Multilingual CMS, WPML String Translation, WooCommerce, and WooCommerce Multilingual & Multicurrency. 2. Switching to a default WordPress theme like Twenty Twenty-Four or Twenty Twenty-Three. However, since these steps are not feasible on the client's production site, we advised a hands-on review by a WPML specialist. The client confirmed that the plugin "Query Monitor – The developer tools panel for WordPress" was the cause of the error; the production site is now working 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 issues persist, please open a new support ticket at WPML support forum.
Problema: O cliente está enfrentando problemas com a não visualização da estrutura do menu em francês na página interna, mesmo após seguir as orientações do assistente de inteligência artificial do WPML, atualizar os plugins, sincronizar o menu pelo WPML e criar um novo menu manualmente. Solução: Verificamos o painel do site do cliente e constatamos que o menu principal está funcionando corretamente e contém todas as traduções, incluindo a do francês. O problema estava na navegação entre os menus e suas traduções, onde o cliente estava visualizando um menu diferente, chamado "menu Français", que estava vazio. Um vídeo foi gravado para explicar melhor a navegação entre os idiomas e esclarecer a confusão: https://www.loom.com/share/d59d0b97e3a14ec08854273b1f55da4b.
Se esta solução não resolver o seu problema ou se ela parecer desatualizada, recomendamos abrir um novo ticket de suporte. Também é altamente recomendável verificar os problemas conhecidos, verificar a versão da correção permanente e confirmar que você instalou as versões mais recentes de temas e plugins.
Problema: El cliente ha añadido reCAPTCHA V3 en varios idiomas en su sitio web, pero frecuentemente este vuelve al idioma original. Además, no puede modificar el reCAPTCHA en el idioma adicional debido a un icono de engranaje que lo impide. Solución: Si estás experimentando problemas similares con reCAPTCHA V3 en un sitio multilingüe con diferentes dominios, no es necesario crear una clave para cada dominio. Simplemente agrega todos los dominios a una sola clave de reCAPTCHA desde el panel de administración de Google. Esta solución ha funcionado para otros usuarios y es independiente de WPML.
Si esta solución no resuelve tu problema, o si parece estar desactualizada o no aplicable a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problem: The client was experiencing an issue where some product categories were not showing in the product filters on the shop page, despite being translated in WPML. This problem appeared after editing a product and running a cache clear and manual crawler.
Solution: We discovered that the issue was related to the 'Hide empty' option in the Bricks template settings. To resolve this, we recommend the following steps: 1) Open the translated template in Bricks. 2) Disable the 'Hide empty' option. 3) Re-enable the 'Hide empty' option. This toggle action helps in making the translated categories appear correctly. Additionally, ensure that the parent category is also selected on each product to avoid issues with categories not showing up. If sorting categories by 'meta numeric value' causes issues, changing the sorting mechanism might help. We also found that the 'Hide empty' option could cause issues even when WPML is disabled, suggesting a potential problem within Bricks itself.
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. Additionally, if further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported a critical issue where the WPML server ams.wpml.org was unreachable, causing a CSS file to fail loading. This resulted in misaligned WooCommerce product columns and a degraded admin interface in WordPress. The client verified the server status using third-party tools and found that the server was not responding. Solution: We confirmed that the ams.wpml.org server is operational and the CSS file at https://ams.wpml.org/mini_app/dashboard.css is accessible. We advised the client to double-check by pasting the URL into their browser. We also requested more details about the issue with the Products list to better understand and address the problem.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: Estás intentando eliminar imágenes que ya no están registradas en la web o dentro de la opción 'Media' como administrador de la web en WordPress, pero estas imágenes aún se visualizan desde la opción 'Media Translation'. Además, aparecen imágenes que nunca has registrado. Solution: Para abordar las imágenes que persisten después de ser eliminadas y las que aparecen sin haber sido registradas, te recomendamos usar la herramienta de sincronización de medios de WPML. Sigue estos pasos: 1. Ve a WPML → Soporte en tu escritorio de WordPress. 2. Desplázate hacia abajo hasta la sección Solución de problemas. 3. Busca y haz clic en el botón Sincronizar adjuntos de medios (puede tardar un momento en procesarse). Después de completar este paso, verifica si las imágenes que eliminaste de la Biblioteca de Medios ya no aparecen en WPML → Media Translation y si las imágenes no registradas han desaparecido.
Si la solución proporcionada no resuelve tu problema o parece irrelevante debido a actualizaciones o diferencias en tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Para más asistencia, visita nuestro foro de soporte.