Problem: El cliente quería personalizar el selector de idiomas para que apareciera como 'Eus / Cas' y como shortcode de texto en un lugar específico de la web, con el color blanco y dentro de un bloque con un contorno alrededor. Además, tenía problemas para visualizar el selector en la versión móvil y quería cambiar el color del texto a negro en esta versión. Solution: Primero, recomendamos al cliente revisar el ticket anterior donde se había tratado un problema similar, disponible en este enlace. Luego, le sugerimos añadir el CSS según se describe en la documentación de WPML, específicamente en la sección de personalización del selector de idiomas, que se puede encontrar aquí: Custom Language Switcher. Para la versión móvil, donde el fondo es blanco y el selector no era visible, recomendamos ajustar el CSS para cambiar el color del texto a negro y asegurarnos de que el selector se visualizara correctamente en todos los dispositivos.
Si esta solución no resuelve tu problema, o si parece no ser relevante debido a actualizaciones o diferencias en tu caso específico, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos en problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: Estás intentando exportar todos los textos de tu sitio web a un archivo Excel para traducirlos de forma masiva y luego subirlos nuevamente. Sin embargo, te encuentras con que el archivo exportado es en formato .po y no sabes cómo convertirlo a CSV. Solution: 1. Para exportar las cadenas de texto, puedes seguir los pasos descritos en este mensaje de un ticket similar: https://wpml.org/forums/topic/exporting-translations/#post-15623432. 2. Después de la exportación, necesitarás buscar una manera de convertir las cadenas a un formato Excel. 3. Como alternativa, ofrecemos la posibilidad de traducir de forma masiva y automática tanto el contenido como las cadenas a través de la traducción automática, que puedes encontrar aquí: https://wpml.org/es/documentation-2/traduccion-automatica-para-contenido-de-wordpress-con-wpml/.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, 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 los temas y plugins. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: You are trying to translate the homepage using the Advanced Translation Editor and notice unrelated text appearing, including dummy content.
Solution: This issue is related to the Bricks builder where orphaned content may not be deleted properly. We recommend checking the following documentation on known issues with Bricks builder regarding orphaned elements: Bricks Builder Known Issues. This problem is expected to be resolved in the next release of the builder.
If this solution does not apply to your case, or if it seems outdated, please open 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, you can contact us directly through our support forum.
Problem: The client is unable to edit their website using WordPress and Elementor Pro due to an error message related to the WPML Sitepress Multilingual CMS vendor code. The error message indicates that headers cannot be modified after they are sent. The issue recurs after an unknown number of page edits, even after deleting and re-adding a user. Solution: We investigated the issue and found that it persists even when the WPML plugin is deactivated, suggesting it is not directly related to WPML. The problem was identified to occur when only the Yoast SEO plugin is active. Updating the Yoast SEO plugin resolved the issue, as demonstrated in a video we shared with the client. If you're experiencing this issue, we recommend trying the following steps: 1. Deactivate the WPML plugin to confirm if the issue persists. 2. If the problem continues, check if it occurs with only the Yoast SEO plugin active. 3. Update the Yoast SEO plugin to the latest version. If these steps do not resolve the issue or if it appears unrelated to the plugins mentioned, it might be due to other factors. In such cases, the solution provided here might be outdated or not applicable to your specific situation. 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 global 404 errors occurring after creating or updating multilingual content and suspects the issue may stem from the WordPress REST API being disabled. They asked whether this could affect WPML's functionality and what REST API requirements WPML has.
Solution:
The supporter clarified that while the REST API must be enabled for WPML to function properly, it is not directly related to the reported 404 error issue.
Problem: El cliente está utilizando el plugin SureCart y desea traducir los productos creados con este, pero no encuentra el signo + para iniciar la traducción en WPML, ni otra manera de hacerlo. Solution: 1. SureCart no es oficialmente compatible con WPML, por lo que no tenemos una guía oficial para traducir productos creados con SureCart. Recomendamos contactar al soporte de SureCart para confirmar si sus productos son traducibles con WPML y, en caso afirmativo, que proporcionen los pasos específicos para hacerlo. 2. Como alternativa, si ya configuraste los productos como traducibles en WPML -> Configuración -> Traducción de tipos de entrada, puedes ir a WPML -> Gestión de traducción. Allí debería aparecer el tipo de contenido 'Productos', donde podrás gestionar las traducciones. 3. Además, te recomendamos incrementar el límite de memoria de WordPress a un mínimo de 128Mb para mejorar el rendimiento. Puedes hacerlo añadiendo el siguiente código en tu archivo wp-config.php:
Coloca este código encima de la línea /* That's all, stop editing! Happy blogging. */. Puedes verificar el límite de memoria actual en WPML -> Soporte.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto irrelevante, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos y verifiques que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: The client is experiencing an issue where the redirection for the Russian language version of their website does not work correctly. Instead of redirecting to wavehouse.ru, it redirects to the English version of the site, wavehousebali.com. Solution: We recommend ensuring that the separate domain mode in WPML is correctly configured, as WPML should handle all redirections without the need for additional plugins or settings. The domains should directly point to the WordPress installation, and WPML will manage the rest. To verify if the domains are set correctly: 1. Go to WPML > Languages in your WordPress dashboard. 2. Check the checkbox next to each domain. 3. Click 'Validate' to see the results. For more detailed guidance, please refer to our documentation on using WPML with different domains per language: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: Si estás experimentando un error 5xx notificado por Google Search Console en la URL de tu sitio y recibes un error de servidor en lugar de la página esperada, es posible que el problema esté relacionado con un error crítico en el plugin Rank Math SEO. Solution: Primero, activa el modo de depuración en WordPress para obtener más detalles sobre el error. Puedes hacer esto añadiendo las siguientes líneas en tu archivo
wp-config.php
justo antes de '/* That's all, stop editing! Happy blogging. */':
Si la solución proporcionada 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 en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: The client is using the GreenShift Builder with WPML to build and translate their website. While translating the homepage using WPML’s Advanced Translation Editor, the translated version displays the default language content instead of the translated content. Additionally, an error in the backend indicates that the block contains unexpected or invalid content, prompting a block recovery message. Solution: We resolved the issue by updating the GreenShift plugin and its add-ons to the latest version. It is crucial to follow the correct WPML translation process and avoid editing the translated content directly in the Gutenberg editor. After these updates and following the proper procedures, we tested the system thoroughly and confirmed that everything is now working as expected.
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 the problem persists, please open a new support ticket.
Problem: Se stai riscontrando problemi nel mantenere lo slug corretto quando passi dal selettore lingua dall'inglese all'italiano sulle pagine PORTFOLIO in AVADA, potrebbe essere dovuto alla presenza di slug duplicati tra le opzioni di AVADA e le impostazioni di WPML. Solution: 1. Assicurati che non ci siano slug duplicati per post type o tassonomie. WordPress non supporta slug duplicati, quindi cambia uno dei due per risolvere il problema. 2. Traduci gli slug in WPML > Impostazione > Traduzione dei tipi di contenuto, anziché in Traduzione stringhe. 3. Elimina le stringhe duplicate da Traduzione Stringhe, poi reimposta gli slug corretti in WPML > Impostazione > Traduzione dei tipi di contenuto. 4. Salva nuovamente le impostazioni in Impostazioni > Permalink per assicurarti che le modifiche siano applicate correttamente.
Se la soluzione proposta non risolve il tuo problema o se ritieni che le informazioni siano obsolete o non applicabili al tuo caso, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di consultare la pagina dei problemi noti e di verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Per assistenza ulteriore, visita il forum di supporto WPML.
Problem: If you're experiencing a critical error message when trying to translate a page using WPML, and you have debug settings enabled in your WordPress configuration, the issue might not be directly related to WPML. Solution: First, check the
debug.log
file in your wp-content folder for any fatal error messages. This will help identify if the issue is with WPML or another plugin. In this case, the error was traced back to the WooCommerce plugin, specifically an unknown format specifier in a PHP file. Since the problem originates from WooCommerce, we recommend contacting WooCommerce support to resolve this issue.
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 with us.
Problem: The client is trying to configure the default language URL format for their site using WPML, aiming to have English as the default language appear under the /en/ directory. However, the current URL format does not include the /en/ for English, showing as https://wpml.proplugin.com/ instead. Solution: We explained that by default, the default language in WPML does not include the language directory in the URL. If the client wishes to include the /en/ directory for the default English language, they need to enable the option "Use directory for the default language". This setting can be found in the WPML settings under the Language URL format options.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related 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.
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.