Problem: Estás realizando tareas de mantenimiento en tu sitio web y te encuentras con una alerta que indica que 'WPML String Translation está habilitado pero no es efectivo porque WPML está desactualizado'. A pesar de que en el listado de plugins todos los plugins de WPML aparecen actualizados, en el panel de webs registradas en WPML no es así y desde WordPress no se permite actualizar. Solution: 1. Para actualizar los plugins de WPML, ve a Plugins -> Añadir nuevo -> Pestaña 'Comercial' -> Haz clic en el botón que aparece arriba para buscar actualizaciones y luego selecciona los plugins a actualizar. 2. Incrementa el límite de memoria de WordPress a un mínimo de 128Mb. Para ello, agrega el siguiente código al archivo wp-config.php que se encuentra en la raíz del sitio:
- Añádelo encima de la línea /* That's all, stop editing! Happy blogging. */ Puedes comprobar el límite de memoria de WordPress en WPML -> Soporte.
Si esta solución no resuelve tu problema o si parece no ser relevante debido a que está desactualizada o no se ajusta 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 temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: Il cliente sta cercando di utilizzare l'editor di Elementor, ma riceve un messaggio di errore e non può accedere alle funzioni di Elementor quando il plugin WPML è attivato. Solution: L'errore riscontrato è:
Errore nell'evento Cron di riprogrammazione per l'hook: elementor_1_elementor_pro_updater_cron, codice di errore: invalid_schedule, messaggio di errore: L'evento programmato non esiste., dati: {"schedule":"elementor_1_elementor_pro_updater_cron_interval","args":[],"interval":300}
. Questo problema non è causato da WPML, ma sembra essere un problema di Elementor che si aspetta l'esecuzione di un cronjob inesistente. È stato segnalato anche nel GitHub di Elementor, senza riferimenti a WPML. Se il problema persiste nonostante l'aggiornamento di Elementor alla versione 3.28.0, che sembra risolvere il problema, ti consigliamo di verificare la versione del fix permanente e di assicurarti di avere installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto. Ti consigliamo inoltre di consultare la pagina dei problemi noti.
Problem:
Client was using custom code where some strings were not being detected for translation, despite using proper gettext methods.
Solution:
It turned out there were unnecessary spaces in the strings and in the related ACF fields. Removing those fixed the problem.
If this solution does not resolve your 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. If the problem persists, please open a new support ticket.
Problem: The client reported that after using WPML's auto-translate feature with Elementor, translations were visible in the back-end but not on the front-end. Specifically, some paragraphs appeared translated while others did not, and headers remained untranslated. Solution: We reviewed the pages and confirmed that the translations for English and German were displaying correctly on both the front-end and back-end. It appears that the issue may have resolved itself or was fixed by the client before our verification. If you're experiencing similar issues where translations are not appearing as expected on the front-end, we recommend: 1. Clearing your browser and site cache. 2. Ensuring that the WPML and Elementor plugins are up to date. 3. Re-saving the Elementor pages in question. If these steps do not resolve the issue, it might be due to a configuration that is no longer relevant or applicable to your current setup. 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 with us for further assistance at WPML support forum.
Problem: Der Kunde konnte nach der Übersetzung von Theme Layouts (Header, Footer, Submenus) mit WPML den Elementor Page Builder nicht mehr öffnen. Der Ladebalken erschien, aber die Seite blieb weiß. Zudem war die Übersetzung nur auf der Desktop-Version sichtbar, nicht auf mobilen Geräten. Solution: Wir haben das WP-Speicherlimit auf der Testseite erhöht. Es wurde zudem ein Fehler im Child-Theme festgestellt, der durch den Wechsel auf das Parent-Theme behoben wurde. Nach dem Wechsel zum Parent-Theme konnten die Inhalte wieder problemlos in Elementor bearbeitet werden.
Falls diese Lösung veraltet erscheint oder nicht auf Ihr Problem zutrifft, empfehlen wir, einen neuen Support-Ticket zu öffnen und die aktuellen bekannten Probleme unter https://wpml.org/known-issues/ zu überprüfen. Stellen Sie außerdem sicher, dass Sie die neuesten Versionen Ihrer Themes und Plugins installiert haben.
Problem: The client is concerned about WPML's WooCommerce Multicurrency feature not creating distinct URLs for each currency, which is recommended by Google for better indexing and structured data management. The client wants to know why WPML uses cookies instead of URLs for currency differentiation and how to configure WPML to create distinct URLs for each currency. Solution: 1. Google's documentation recommends, but does not require, distinct URLs for each currency. Many e-commerce sites successfully use dynamic currency switching without separate URLs, focusing instead on ensuring that the structured data matches the displayed price. 2. By default, WPML changes currency using cookies and user sessions to avoid duplicate content and simplify store management. WooCommerce itself does not support separate URLs per currency. 3. To display different currencies based on the site's language (resulting in separate URLs), follow these steps: - Go to WPML > Languages. - Select "Different languages in directories". - Go to WooCommerce > WooCommerce Multilingual > Multi-currency tab. - Enable "Show prices in different currencies based on site language." This setup links currency to language, but each language must have a unique currency. 4. For custom URL structures like example.com/usd/product/, custom development is necessary. A developer can modify the URL structure, update structured data dynamically, and set up canonical tags to prevent duplicate content issues. We recommend hiring a developer experienced in WooCommerce and WPML customization from https://wpml.org/contractors/. 5. Ensure your structured data is correct by using tools like Google's Rich Results Test and verifying that SEO plugins handle currency display accurately.
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 further assistance is needed, please open a new support ticket at WPML support forum.
The client added 'Filipino' as a new language and manually translated several pages including the homepage. However, the Filipino flag did not appear in the dropdown for the homepage, although it did for other pages.
Solution:
First, we advised the client to ensure that the homepage was fully translated to Filipino by checking the translation status in Pages>>All Pages. We suggested creating a test post in English, duplicating it to Filipino, and then checking if the language switcher worked as expected on this post.
Upon further investigation, it was found that the English homepage had not been translated into Filipino, but a new, separate Filipino homepage had been created. As a solution, we recommended linking the Filipino homepage with the English version after taking a backup, as described in our documentation: How to link already translated pages.
If this solution does not resolve your 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 you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problema: El cliente enfrentó un problema donde, tras copiar su sitio web, WPML detectó el sitio como nuevo a pesar de mantener el mismo dominio. No pudo redirigirse a la sección para obtener el código de migración necesario para conectar los créditos de traducción automática entre ambas versiones del sitio. Solución: 1. Seleccionar la opción 'No/Cambié la dirección del sitio a esta nueva' en el banner de migración de WPML. 2. Incrementar el límite de memoria de WordPress a un mínimo de 128Mb. Para esto, agregar el siguiente código en el archivo wp-config.php:
Este código se debe añadir 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 parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar 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 attribute values disappear when editing a WooCommerce product in a secondary language using the WordPress editor. This occurs even if no changes are made to the product and it is simply saved again. Solution: We recommend continuing to use the Advanced Translation Editor (ATE) for editing products. The issue arises because the products were initially translated using ATE, and editing them with the WordPress editor can overwrite the ATE translations. To avoid losing translated content, it is best to maintain the use of ATE for all product updates.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please visit our support forum to 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.
