Problem: The client needs to change the original language displayed in the WPML Advanced Translation Editor for a translator who does not speak the original language of the content. The content was initially in French, and the translator needs to see English on the left side instead of French when translating to Arabic. Solution: We explained that it is not possible to change the language displayed on the left side in the Advanced Translation Editor. This side always shows the default language in which the page was initially created. If you're experiencing this issue and need the translator to view a different source language, unfortunately, this cannot be adjusted for translations already done. For new translations, ensure the translator's settings are correctly set to translate from the desired source language.
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.
Problem: The client is attempting to manually change a link URL using the Advanced Translation Editor (ATE) but is unsure if the process described in the documentation is still applicable with the latest version of ATE. Additionally, the client faces issues when trying to filter a link in a Divi module in the Divi Library. Solution: We confirmed that it is still possible to manually change link URLs with the latest version of the Advanced Translation Editor by searching for the URL in ATE and manually translating it. For issues related to filtering links in Divi modules, we suggested creating a custom XML configuration code for the module to override the default WPML feature and translate the URL in ATE. For further guidance, refer to the documentation on Maintaining Divi Builder Compatibility with WPML.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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, please visit our support forum at WPML Support Forum.
Problème : Le client travaille sur le site en utilisant WPML et cherche à accéder aux phrases non validées dans l'ATE pour terminer la traduction. Il souhaite pouvoir filtrer les phrases non encore traduites directement dans l'ATE, similaire à l'ancienne fonctionnalité de l'éditeur classique V1. Solution : Nous avons suggéré d'utiliser les outils de navigateur ou une extension de navigateur pour modifier la classe CSS
.AT-segment_list__add_translation_container
. Cette classe est présente uniquement sur les blocs en attente de traduction, permettant ainsi de les mettre en évidence en changeant la couleur d'arrière-plan. Nous avons recommandé l'extension Chrome Visual CSS Editor qui permet de modifier les paramètres CSS de ces éléments sans coder.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous invitons à consulter les problèmes connus, vérifier la version des correctifs et vous assurer que vous avez les dernières versions des thèmes et plugins installés. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem:
PHP Fatal error: Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in ...m/wp-includes/blocks.php:1409 When enabling "Scellius for WooCommerce" plugin with PHP 8
Solution:
The error was happening due to the settings being corrupted.
To fix this, We went to the site database wp_options table and searched for the option name "woocommerce_scelliusstd_settings" and renamed it to "woocommerce_scelliusstd_settings_old", this stored the plugin settings.
