Available Solutions

Problem:
The client's website went offline after an update, displaying a WordPress error related to WPML, specifically an undefined method

WP_Textdomain_Registry::reset()

. Additionally, the client mentioned issues with the WPML key not being accepted and an error message stating that WPML cannot connect to wpml.org.

Solution:
For the error involving

WP_Textdomain_Registry::reset()

, we provided a custom search URL to help the client find existing tickets with the same issue that contain solutions:
https://www.google.com/search?q=site%3Awpml.org%2Fforums+%22WP_Textdomain_Registry%22
This issue is likely due to the client using older versions of WordPress, WPML, and the WPML String Translation add-on.

Regarding the other issues, we adhere to our Support Policy of handling only one issue per ticket to maintain focus and efficiency. Therefore, we created two separate tickets for the remaining issues:

• https://wpml.org/forums/topic/split-site-key-doesnt-match-invalid-site-key/
• https://wpml.org/forums/topic/split-the-wpml-plugin-cannot-connect-to-wpml-org-2/

The client will be notified via email when there are answers to these tickets.

Please note that the solution provided here might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket.

Problem:
The client is trying to reduce the size of the

icl_translate

tables by looking for a delete jobs plugin.
Solution:
We recommend backing up the site before proceeding with any changes. After ensuring that the site is backed up, we suggest following the guidance in the forum ticket at WPML delete jobs plugin - very large icl_translate table.

Please note that the solution provided might be outdated or not applicable to your specific case. If after checking the related known issues at https://wpml.org/known-issues/ and confirming that you have the latest versions of themes and plugins installed, the problem persists, we encourage you to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.

Problem:
The client has a website originally in English and added Russian and Estonian translations. The client wants to make Estonian the default language and encountered issues when updating content. The translation screen did not reflect Estonian as the default language, and changes made there would overwrite previous translations.
Solution:
We explained that switching the site's default language does not change the source language of the content. If the content was originally created in English, it would remain the source language for translations. Therefore, any content updates should be made in English first and then translated into the other languages. If the client finds that this solution does not apply or is outdated, we recommend opening a new support ticket. Additionally, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed.

If further assistance is needed, please contact our support forum at https://wpml.org/forums/forum/english-support/.

Problema:
El cliente intenta activar su suscripción de WPML en su nuevo sitio web y está siguiendo la guía de configuración.
Solución:
Si estás experimentando problemas para activar tu suscripción de WPML en tu nuevo sitio web, te recomendamos que sigas la guía de configuración proporcionada en los siguientes enlaces:

• https://wpml.org/faq/install-wpml/#register
• https://wpml.org/faq/install-wpml/

En este caso particular, nuestro equipo de Sistemas se encargó del problema y lo resolvió. Te pedimos que intentes activar tu suscripción nuevamente.

Es posible que esta solución sea irrelevante porque está desactualizada o no se aplica a tu caso. Si es así, te sugerimos abrir un nuevo ticket de soporte. También recomendamos encarecidamente revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que has instalado las últimas versiones de temas y plugins.

Si necesitas asistencia adicional, por favor, contacta con nosotros en el foro de soporte de WPML.

Problem:
The client was experiencing an issue where variation gallery images in WooCommerce products were not displaying in the translated version of the product. Instead, the main product image was shown.

Solution:
1. We suggested checking the translation preference for the Variation image gallery upload field. This can be done by navigating to WPML > Settings > Custom Field Translation and setting the translation preference to "Copy".
2. We requested the WPML Debug Information from the client to further investigate the issue. Instructions on how to obtain this information can be found here: https://wpml.org/faq/provide-debug-information-faster-support/.
3. For the issue with the attribute 'Taglia' not appearing correctly in the translated product, we found that the Text Swatch option in the Translated Attribute term was deactivated. Activating this option resolved the issue, and the variations began displaying correctly.

If you're experiencing a similar issue, we recommend trying the steps outlined above. However, please note that the solution might be irrelevant due to being outdated or not applicable to your case. If these steps do not resolve your issue, 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: https://wpml.org/forums/forum/english-support/.