Problème : Le client a traduit des catégories de Français vers Arabe sur son site web en utilisant WPML, mais les images des catégories traduites ne sont pas les mêmes que celles de la version originale. Les catégories en version arabe n'ont aucune image. Solution : 1. Assurez-vous d'avoir installé et activé WPML Media Translation et WooCommerce Multilingual & Multicurrency. 2. Accédez à
et testez les deux options indiquées pour résoudre le problème. 3. Si le problème persiste, essayez de changer les images des catégories directement dans la version traduite. 4. Vous pouvez également tester les options dans la traduction des médias, bien que cela n'affecte généralement pas les champs personnalisés de taxonomie.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier 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 sur notre forum de support.
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.
Problem: If you're unable to activate the WooCommerce Multilingual & Multicurrency plugin due to a 'fatal error activation', it might be due to a conflict with another plugin, such as 'WP Rocket'. Solution: We recommend that you access your server via FTP and open the
wp-config.php
file located at the root of your WordPress installation. Insert the following lines just before
Please note that this solution might be outdated or not applicable to your specific 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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the French translations for WooCommerce are not appearing correctly on their site. Despite setting the site to French, many strings remain in English. The client uses a custom Default locale (fr_DZ) which does not match the WooCommerce provided locale (fr_FR). Solution: 1. Change the file name of the translation file. Using the file manager in the WordPress installation, navigate to
/wp-content/languages/plugins
and rename the file
woocommerce-fr_FR.mo
to
woocommerce-fr_DZ.mo
. 2. Alternatively, in WPML -> Strings Translation, search for the field and manually translate it. 3. Adjust the "Default locale" setting in WPML. Go to WPML -> Languages -> Site Languages, click "Edit languages", and change the "Default locale" from fr_DZ to fr_FR, while keeping hreflang as fr_dz. This ensures the correct .mo file is used without affecting the site's front end or SEO.
It is crucial to make a full site backup (files and DB) before proceeding with these steps.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: WCML shows the default currency, regardless of location. Solution: If you're experiencing this issue, we recommend continuing to use WP Rocket instead of switching to Siteground Optimizer. Ensure that both the WPML and WCML plugins are active, as WP Rocket requires these to function correctly with WooCommerce Multilingual. For a detailed view, please check this specific line of code.
Please follow these steps: 1. Use FTP or File Manager to access your site's file system. 2. Navigate to /wp-contents/wp-rocket/inc/3rd-party/plugins/ecommerce and open "woocommerce-multilingual.php" in the editor. 3. Replace the code on Line 10:
4. Save the changes, clear both your site and browser's cache, and then test again.
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 reported that the search bar in the Arabic version of the site stopped working for logged-out users, while it worked fine for logged-in users. The issue was not related to cache and persisted even with minimal plugins active.
Solution:
1. We activated the 'Language filtering for AJAX operations' option in WPML -> Languages, as it is necessary for AJAX operations.
2. We identified that the 'wp-wpml_current_language' cookie was not being set upon language switch, but it worked after visiting a page.
3. We advised the client to clear the website's cache on the server-side.
4. We suggested testing the issue in a minimal setup, keeping only the theme, WPML plugins, WCML plugins, and must-have plugins active, while disabling all others.
If you're experiencing a similar issue, we recommend you try the steps above. However, the solution might be irrelevant due to being outdated or not applicable to your case. In such instances, 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 the problem persists, please open a new support ticket with us.
Problem: The client reported that the same string appears translated on one page but not on another. Specifically, header elements were translated on the home page but not on a product page, despite the Siteground cache plugin being disabled and the server cache being cleared.
Solution: 1. We checked and found that the menu items coming from the Customizer were not registered as strings and displayed dynamically, which caused issues when the site's default language was not English. 2. We set the default permalinks related to WooCommerce to French, the site's default language, via Settings > Permalinks. 3. We translated the slugs at WooCommerce > WooCommerce Multilingual & Multi-Currency > Store URLs. 4. On a local copy of the site, we updated our plugins which resolved the issue. We instructed the client to check for updates by going to Plugins > Install > Commercial and clicking "Check for updates". 5. If updates were not visible, we provided a link to manually download them from https://wpml.org/fr/account/downloads/ and advised to click "Télécharger WPML manuellement". 6. After updating, we suggested reapplying the translation of the strings.
If the provided solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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 contact us in the WPML support forum.
Problem: The client's store default language is French, and they have set the currency to DZD. They encountered three issues: changing the currency symbol for French, correcting the display of numbers in Arabic, and positioning the currency symbol correctly in Arabic. The first two issues were resolved, but the third issue caused the numbers to display incorrectly again.
Solution: We advised the client that the settings and custom work they are trying to apply would be the same even if they were not using WPML and that it is more related to WooCommerce hooks/code. We recommended that they could hire a developer for custom code if needed. However, we also provided a suggestion to use specific CSS classes for the price and symbol in the Arabic language to adjust the amount direction and symbol separately, rather than using a class that alters both.
Please note that the solution provided might be irrelevant due to being 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 reported that strings from WooCommerce that should be automatically translated by WPML, such as the "Add to Cart" button, were not synchronized and required manual translation.
Solution:
Please try one of the workarounds after a site backup to fix this issue.
Step 1: 1) Go to WPML>>Themes and Plugins localizations. 2) Scan for strings in the child theme (named *Web Rocket*) and the *Flatsome* parent theme. 3) Scan for the *WooCommerce* strings. 4) Check if the issue still persists.
Step 2: 1) Navigate to WPML>>String Translation and ensure you have a full site backup. 2) Enable the *Look for strings while pages are rendered* option in the *Auto register strings for translation* section (found at the bottom of the screen). 3) Visit the frontend pages to see if the issue with strings like *Add to Cart* is resolved. Note that this option will automatically disable itself after a few hours.
Please be aware that this solution might not be relevant if it's outdated or not applicable to your case. If the issue persists, we 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 was experiencing an error indicating that the
product_type
field was set incorrectly for some product translations due to the
product_type
taxonomy being translated.
Solution: We advised the client to first take a full backup of their site. Then, to resolve the issue, we instructed them to navigate to the WooCommerce Multilingual troubleshooting page and click on the "Start" button under "Fix product_type taxonomy terms". We also confirmed that the client's settings for the
product_type
taxonomy were now correct according to the screenshot they provided. Additionally, we clarified that the warning in their screenshot was a reminder to back up their site before proceeding with any troubleshooting steps. For more details, we provided a link to our documentation: WPML Troubleshooting Options.
Please note that if this solution does not apply to your case, or if it is outdated, we recommend checking the 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 you still need assistance, please do not hesitate to open a new support ticket with us.
