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.
Problem: The client was trying to translate a product template in the Divi Theme Builder but encountered an issue where the translated template would apply to both the French and English versions, regardless of the language loaded in the Theme Builder.
Solution: 1. We recommended the client to back up their site. 2. Navigate to WPML > Support > Troubleshooting. 3. Click on the buttons provided, including the one to synchronize templates. 4. If the issue persisted, we requested temporary access to the client's wp-admin and FTP for further investigation. 5. We also mentioned the possibility of using the Duplicator plugin to replicate the site locally for troubleshooting.
We were able to resolve the issue by synchronizing the templates from WPML > Support > Troubleshooting options.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket with us.
Problem: If you're experiencing issues with translating a product template body in the Divi Theme Builder, where changes apply to all languages instead of just one, or if your footer appears in English on both language versions without any recent modifications, follow the steps below. Solution: First, ensure that you are working in the correct language environment: 1. Go to Divi -> Theme Builder. 2. Switch the language to the one you want to edit (for example, English). 3. Add or modify the custom body template. 4. Save the changes. If the problem persists, check your WPML settings: 1. Navigate to WPML -> Settings -> Post Type Translation section. 2. Set the "Theme Builders (et_theme_builder)" to "Not Translatable". 3. Click "Save". 4. Return to Divi -> Theme Builder. 5. Add or select the templates you wish to use. 6. Save your template. 7. Translate the templates using WPML -> Translation Management. By setting the 'et_theme_builder' post type to 'Not Translatable', you prevent the issue of a single language change affecting all languages. If this solution doesn't look relevant to your issue, please open a new support ticket with us.
Problem: The client is trying to display translated strings on their WooCommerce page but is seeing French strings instead of the expected English ones. Solution: We recommend checking if the strings were generated by a WooCommerce extension or if they are default WooCommerce strings. The client should try to remove the strings, register them again, and then translate them. To auto-register strings, we suggest following the instructions in our documentation on finding strings that don't appear on the String Translation page.
