mohamed-nawfelO

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

file located at the root of your WordPress installation. Insert the following lines just before

:

After making these changes, try activating the plugin again. If the problem persists, check the

file in the /wp-content directory for any specific error messages that could help identify the issue. For more information on debugging in WordPress, visit https://wordpress.org/support/article/debugging-in-wordpress/.

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 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 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.