Problema: El cliente necesita cambiar el registro del plugin WPML a su nueva cuenta sin perder las traducciones y configuraciones existentes en su sitio web, después de haber migrado el sitio a un nuevo servidor y haber obtenido un nuevo código de registro. Solución: Si estás experimentando esta situación, te recomendamos seguir estos pasos para cambiar el registro de WPML a tu cuenta: 1. Crea una copia de seguridad del sitio completo. 2. En tu sitio, ve a Plugins -> Añadir nuevo -> Pestaña 'Comercial' -> Elimina el registro del sitio. 3. Al hacer click en registrar el sitio, te aparecerá un enlace justo debajo del campo donde debes pegar la llave. 4. Este enlace te llevará a https://wpml.org/es/account/sitios/ donde debes crear una nueva llave de registro. 5. Utiliza esta nueva llave para registrar el sitio en Plugins -> Añadir nuevo -> Pestaña 'Comercial'. Siguiendo estos pasos, tu sitio estará registrado correctamente en tu cuenta y funcionará sin problemas.
Es posible que esta solución pueda ser irrelevante si ya no es aplicable o si no se ajusta a tu caso. Te recomendamos revisar los problemas conocidos, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Si después de seguir estos pasos aún necesitas ayuda, por favor, abre un nuevo ticket de soporte.
Problema: Estás intentando traducir productos de WooCommerce en tu sitio web usando WPML, pero no aparecen los productos en español para traducir en el plugin. Solución: 1. Asegúrate de que estás utilizando el filtro correcto en el plugin de WooCommerce de WPML. Cambia el filtro como se muestra en la captura de pantalla que te hemos enviado para ver si los productos aparecen. 2. Incrementa el límite de memoria de WordPress a un mínimo de 128Mb. Puedes hacer esto añadiendo el siguiente código en tu archivo wp-config.php:
Añade este código justo 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 obsoleta, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos 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 was concerned about the unprofessional and system-generated appearance of the URL slug 'wp-global-styles-unisved-12' for a page, which did not match the expected descriptive and cleaner 'om-oss' similar to its Polish counterpart. Solution: We reviewed the WPML settings and confirmed that the 'Auto-generate from title (default)' option was selected, which should automatically generate the slug based on the page title. It appeared that the slug might have been manually altered on the Swedish page's editing screen. We corrected the slug to 'om-oss' to match the expected format. We asked the client to confirm if the issue was resolved.
If this solution does not apply to your case, or if it seems outdated, we 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. Should the problem persist, please open a new support ticket.
Problem: You have updated the homepage in English, including text, pictures, and layout, but the changes are not reflecting on the translated pages, causing them to appear disorganized. Solution: We recommend retranslating the homepage so that the recent changes can be properly copied over to the translated pages. This involves updating the translation for each language to ensure all modifications are synchronized across your multilingual 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: Der Kunde betreibt eine zweisprachige WordPress-Website mit WPML in einer Multidomain-Konfiguration und benötigt Unterstützung bei der Integration des Plugins 'Brevo for WooCommerce'. Beim WooCommerce-Checkout sollen Nutzer den Newsletter abonnieren können, wobei die Eintragungen sprachabhängig unterschiedlichen Listen in Brevo zugewiesen werden sollen: DE-Newsletter-Liste → ID: 2, EN-Newsletter-Liste → ID: 9. Trotz des Einsatzes eines Filters, der die aktuelle Sprache berücksichtigt, wird beim Checkout auf der englischen Seite weiterhin nur die deutsche Liste verwendet. Solution: Da in diesem sepziellen Fall auf der Brevo-Plattform nur eine Liste pro Formular angewendet werden kann, gibt es von unserer Seite aus leider keine Möglichkeit, darauf Einfluss zu nehmen. Man kann alternativ die Formulare direkt in WordPress anlegen, sie übersetzen und jedem Formular eine eigene List zuweisen.
Bitte beachten Sie, dass diese Lösung möglicherweise irrelevant ist, da sie veraltet sein könnte oder nicht auf Ihren Fall zutrifft. Wir empfehlen Ihnen, neue Support-Tickets zu öffnen, wenn dies der Fall ist. Überprüfen Sie außerdem die bekannten Probleme, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.
The admin user named 'm***u' is unable to view the Translations queue in the WPML Translations menu, as it appears empty.
Solution:
First, verify if the translations are already assigned to another translator by navigating to WPML >> Translation Management >> Translation Jobs.
Next, ensure that 'm***u' is added as a Translator in WPML >> Translation Management >> Translators. For further guidance, refer to the WPML documentation on admin capabilities and working as a reviewer:
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, visit our support forum at WPML Support Forum.
Problem: You are encountering an issue where sidebar widgets disappear on .xml 404 pages within a language directory, while they appear as expected on regular 404 pages. This problem is observed in a setup using WPML with the WPML SEO plugin and a Genesis child theme. Solution: We have investigated and determined that this issue is likely not related to WPML directly. It appears to be associated with how templates are loaded for non-PHP files, such as XML. If you're experiencing this issue, we recommend checking your theme or server configuration to ensure that XML pages are handled correctly. Additionally, verify that your theme supports widget display on XML-generated 404 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. If problems persist, please open a new support ticket.
Problem: The client reported that their website, which uses the ACF plugin, experiences freezing during the save process when WPML is active. The error message displayed is "Application did not respond in time." This issue does not occur when WPML is deactivated. Solution: We investigated the issue by testing without WPML, ACFML, and with a default theme. The problem persisted, indicating it is not solely related to WPML. We observed that the issue might be related to server resource limitations such as PHP memory limit or server response time. We recommend: 1. Checking the PHP error logs for detailed information on failures. 2. Consulting with hosting support to possibly increase server resources. 3. Considering an update to the PHP version. For issues related to slow performance or increased queries, we suggest consulting this carefully curated list of items. If the problem persists after improving server resources, and you suspect WPML might still be impacting performance, please let us know.
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, we encourage you to open a new support ticket at WPML support forum.
Problem: The client is facing an issue where the automatic currency conversion rate update is not working as expected on their website. They are concerned about potential conflicts due to having over 40 plugins installed. Solution: We recommend the following steps to troubleshoot and resolve the issue: 1) Ensure that WooCommerce and WCML are updated to the latest versions. Before making any changes, take a full backup of your website and database. 2) Deactivate all plugins except for WPML, String Translation, WCML, and WooCommerce. 3) Switch to a standard theme, such as Twenty Twenty-Four or Twenty Twenty-One. 4) Check if the issue still occurs. 5) Reactivate the plugins one by one, checking for the issue after each activation to identify any conflicts. 6) If the issue does not reappear after all plugins are activated, switch back to your original theme to check if it is the cause. Additionally, consider that cron jobs require time to run, typically scheduled every 24 hours. You can use cron manager plugins from WordPress.org to manage and test cron jobs. For further debugging, enable WPML's debugging feature as described at https://wpml.org/documentation/support/debugging-wpml/ and monitor the /wp-content/debug.log file for any errors during the cron job execution.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, please visit our support forum at https://wpml.org/forums/ 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.
Problem: If you're experiencing repeated '/en/' in your URL while using WPML, it might not be an issue with WPML itself. This problem could be due to server-side errors that occur when headers are sent before the output, especially when the URL includes a language code like '/en' or '/fr'.
Solution: We recommend checking your server for any errors that might be outputting before headers. This issue occurs in both the frontend and backend, regardless of whether debugging is on or off.
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 known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.
Problem: The client reported issues with translations not showing correctly after renaming a custom post type from 'Products' to 'Places'. Specifically, the English versions of the pages were not appearing, and tags were displayed in both English and Arabic instead of only English. Solution: Renaming custom post types with existing content can lead to unexpected behavior, including issues with translation associations and language metadata. To address potential database inconsistencies caused by the renaming:
Check
wp_posts.post_type
to ensure all translated entries are still listed as 'product'.
Verify
wp_postmeta.meta_key
for keys like _wpml_word_count and _wpml_media_duplicate to confirm they're intact.
Ensure
icl_translations.element_type
is set to 'post_product' for all translations.
Confirm the correct language assignment in
icl_translations.language_code
.
Make sure translated posts share the same Translation ID (trid) as the originals in
icl_translations.trid
.
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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
