Problema: El cliente estaba intentando aplicar traducciones en su sitio web usando WPML, pero al guardar, los cambios no se aplicaban correctamente. En particular, al traducir al español, el contenido seguía apareciendo en inglés en varias páginas. Solución: Primero, verificamos si el problema se debía a la utilización de un método de traducción incorrecto que el Editor de Traducción Clásico (CTE) estaba sobreescribiendo. Sugerimos realizar los siguientes pasos: 1. Editar la página en el idioma original. 2. Hacer un pequeño cambio en el contenido, como añadir un punto final. 3. Guardar los cambios para refrescar el estado de la traducción. 4. Actualizar las traducciones. Además, aplicamos un workaround descrito en la página de errata de WPML para problemas específicos con el CTE, que se puede encontrar aquí: https://wpml.org/errata/editing-translations-with-classic-translation-editor-cte-may-break-with-wpml-4-7/ Si después de seguir estos pasos el problema persiste o la solución propuesta no es relevante debido a actualizaciones o diferencias en el caso específico, recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que se han instalado las últimas versiones de los temas y plugins.
Problem: You are encountering an error related to the load textdomain function, specifically with the message: Notice: Function _load_textdomain_just_in_time was called incorrectly. This issue appears only in the FR and ES languages and is linked to the Favorites plugin, which your theme requires. Solution: This error is due to recent changes in WordPress. We recommend ensuring that the Favorites plugin is updated to the latest version to resolve this issue. For more detailed information, please visit the following link: WPML Errata on PHP Error in WP 6.7.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML 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: You are trying to ensure that shipping discount rules remain active across all frontend languages in WPML. The discount rule works perfectly in the Dutch version of your webshop, but when the checkout page is translated (e.g., to French), the rule is no longer applied. Solution: We recommend checking the known issue related to shipping methods not appearing on translated cart pages at https://wpml.org/errata/flexible-shipping-pro-shipping-methods-do-not-appear-on-translated-cart/. Additionally, ensure that you have updated your WPML plugins to the latest version to avoid any conflicts or incompatibilities. It is crucial to take a full backup of your website and database before making changes. We also advise trying these steps on a staging or development site first to protect your live website.
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 at WPML support forum.
Problem: You are experiencing an issue when switching from English to French on your website, receiving an error message indicating that the translation loading for the health-check domain was triggered too early. This suggests that some code in a plugin or theme is running prematurely. Solution: We recommend ensuring that all your plugins, especially the one mentioned in the error message, are updated to their latest versions. You can check for updates in the 'Plugins → Add New Plugin → Commercial' tab by clicking the 'Check for updates' button. Additionally, updating the WPML plugin to the latest version, which is 4.7.1, might help as it includes the latest bug fixes and improvements. For detailed instructions on updating WPML, please visit http://wpml.org/faq/install-wpml/. For more information on this specific error, you can visit https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the 'Stores' section on their profile page does not load in the Serbian version and shows a spinning loader, while the English version loads correctly. The problem is associated with the Classified Listing Store plugin, and the slug is set to 'store'. Solution: We recommended applying a workaround from our errata page. You can find the detailed steps and explanation here: WPML String Translation error fix.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client reported that the English version of their website was displaying mixed content in English and French, including forms and property details. This issue seemed related to the translation settings in the theme's backend, where languages were mixed without any recent changes made by the client.
Solution: We advised the client to ensure they are using the latest versions of the WPML plugins by checking for updates in the Plugins > Add New > Commercial section. We also suggested re-adding strings in the default language and re-translating them to check if the issue persists. Additionally, we recommended not translating labels from the theme options but using the WPML String Translation instead. If the problem continues, we suggested creating a staging site for further debugging to avoid issues on the live 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 for personalized assistance.
Problem: The client experienced a significant increase in the size of the icl_translation table after switching from Elementor to Gutenberg/GeneratePress, causing delays in staging software due to the large database size. The client also inquired about the creation and loading of .mo files for translations. Solution: We can offer installing a special plugin to manage and delete unnecessary jobs that may be enlarging the database. Our developers are aware of this issue and are working on a solution in a future version of WPML.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
Problem: You are unable to add a different URL in a Custom Post Type field for the English version of your website, as the URL field is blocked. Solution: We recommend checking the workaround provided on the Advanced Custom Fields - Inability to Translate External Links in Same Fields Across Languages page. This should help you unlock the URL field and allow you to add different URLs in your Custom Post Types.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problème: Après avoir traduit les templates "Header" et "Footer" via Translation Management, une erreur 500 apparaît lors de l'accès aux pages traduites. Le client a reçu un message d'erreur indiquant un "Crash du site web". Solution: 1. Nous avons recommandé d'activer le journal de débogage de WordPress pour identifier les erreurs potentielles. Pour cela, modifiez le fichier wp-config.php comme suit:
2. Après avoir activé le débogage, une erreur liée au plugin jet-compare-wishlist a été identifiée. Nous avons conseillé de désactiver ce plugin pour résoudre le problème. Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de consulter les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
