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.
Problem: The client is not receiving notifications and experiences delays in displaying translation changes, despite clearing WordPress cache, browser cache, and deactivating hosting CDN. Solution: We recommend checking the notification settings in the top bar of the ticket conversation.
Problem: The client reported that translations do not update instantly, and this issue persists even in a minimal environment. It affects both pages and posts. Additionally, the client receives a message stating, "Translation successfully completed. Please return to your site manually, as we couldn't redirect you automatically." Solution: We accessed the client's website and performed the following steps to verify the issue: 1. We navigated to the Pages tab and opened the editor for a specific page. 2. We edited the Spanish translation of the page, changed the title, and saved the changes. 3. We then checked the corresponding Spanish page and confirmed that the changes were reflected instantly. We recommend the client to verify if the website is functioning correctly now. If the issue persists, we suggest recording a video demonstrating the problem using Loom, which is free and easy to use.
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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. For further assistance, you can also contact us directly at the WPML support forum.
Problem: The client reported a styling issue on the English version of their website, specifically on a certain page, which differed from other languages. Additionally, the client inquired about a feature in the translation editor to automatically display strings that are not translated or not checked yet. Solution: We updated the translation to address the styling issue. For the translation editor query, we recommend using filters available in the WPML translation management system to display untranslated or unchecked strings. This can streamline the process of finding and translating missing strings.
If this solution does not resolve your issue or seems outdated, please check the related known issues and verify you have the latest versions of themes and plugins installed. If the problem persists, we encourage you to open a new support ticket.
Problème : Le client ne parvient pas à afficher la version anglaise de la bannière des cookies Complianz, malgré les chaînes étant bien traduites. Après une mise à jour de WPML, la bannière ne s'affiche qu'en français, même sur la version anglaise du site. Solution :
- Mettre à jour les champs dans "Complianz > Bannière" en ajoutant un espace à la fin du texte puis sauvegarder. - Aller dans "WPML > Localisation du thème et des plugins", sélectionner le plugin Complianz et cliquer sur "Analyser les plugins sélectionnés". - Ensuite, aller dans "WPML > Traduction de chaînes" pour revalider les traductions. - Enfin, purger le cache pour voir le résultat sur le frontend.
Il est possible que cette solution ne soit plus pertinente, soit parce qu'elle est obsolète, soit parce qu'elle ne correspond pas à votre cas. Nous vous recommandons de consulter la page des 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 sur notre forum d'assistance.
Problem: If you're experiencing issues with WooCommerce custom fields not displaying in secondary languages on your product pages, we have identified a solution.
Solution: Firstly, ensure that the 'Product Fields (wccf_product_field)' post type is set to Translatable in WPML -> Settings -> Post Types Translation. Then, follow these steps: 1. Go to your product fields. 2. Edit the field in the default language. 3. In the 'Language' section of the right sidebar, click the + icon to add a translation of the field. 4. Translate only the label in the Advanced Translation Editor (ATE) and return to the default language version of the product. 5. Switch to the secondary language from the top admin bar and edit the field, adding conditions and settings to match the default language version.
Alternatively, you can create separate fields for each language without using ATE, which allows for clearer naming of fields and easier management.
If you encounter a 500 Internal Server Error when selecting options from the field, it may be necessary to delete problematic fields, clear the trash, and recreate them one by one, ensuring to translate and synchronize attributes. Also, consider disabling caching and firewall systems while testing.
Please note that this solution may be outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket with us.
