Problème :
Le client a rencontré un message d'erreur indiquant que l'éditeur de traduction avancé WPML ne fonctionnait pas et ne pouvait pas se connecter. De plus, le client avait des problèmes pour traduire certains textes sur son site web.
Solution :
Pour le problème de connexion de l'éditeur de traduction, nous avons identifié que le champ obligatoire 'display name' de l'utilisateur WordPress était vide, ce qui empêchait la communication avec notre service. Nous avons résolu ce problème en remplissant ce champ.
Problem: The client's team of developers has an automatic algorithm for updating products from a CRM system. They encountered an issue where prices and quantities in translated products are not automatically synchronized with the main language when using the
WC_Product::save()
method. Solution: We recommend using the REST API to update products, as it should synchronize correctly. Alternatively, the client can utilize the
save_post
or
update_post
hooks to trigger synchronization. We also suggest looking into syncing custom fields between products using their own hooks. For further reference, the client can check out a similar case:
Problem: The client's Contact Form 7 (CF7) forms were disappearing from the dashboard after installing/activating the Contact Form 7 Multilingual plugin. Even after deactivating the plugin, the forms did not reappear in the dashboard, although they were displaying correctly on the frontend. Solution: If you're experiencing disappearing CF7 forms in the dashboard after translating them or using the Contact Form 7 Multilingual plugin, we recommend the following steps: 1. Go to WPML >> Support >> Troubleshooting page. 2. Click the following buttons to set the language information correctly:
Clear the cache in WPML
Remove ghost entries from the translation tables
Set language information
After performing these actions, the forms should reappear in the backend. For more details, you can refer to our documentation on WPML troubleshooting options here: WPML Troubleshooting Options
Problem: If you're experiencing a 404 error when adding a product to the cart on your multilingual site, and this only occurs in a secondary language like Spanish, it might be related to a known issue with the Jetpack plugin. Solution: We recommend trying the workaround mentioned in our Errata page for a similar issue with Jetpack. You can find the instructions here:
If you're not comfortable making changes to PHP files or implementing the workaround yourself, we can assist you. Please ensure you back up your site files and database before proceeding. If the solution provided in the Errata does not resolve your issue, or if you need further assistance, please open a new support ticket with us.
Problem: If you're experiencing issues with lightbox functionality not working on translated pages, while it works on the original page, this might be due to a recent problem that has arisen.
Solution: We recommend trying the following steps: 1. Ensure that the Simple Lightbox plugin's JavaScript code handles URLs correctly. 2. Modify the code in the file
by replacing the existing code with a new version that decodes HTML entities and encodes the URL properly. 3. If you're not comfortable making these changes yourself, please share this workaround with the Simple Lightbox plugin author and suggest they join our Go Global program, where our Compatibility developers will assist in making their product compatible with WPML.
For more details on the Go Global program, please visit: Go Global program.
If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us for further assistance: WPML support forum.
Problem: The client was experiencing a fatal error when switching to Spanish content, with an error message indicating an 'InvalidArgumentException' Solution: We're not sure about what's causing the issue because our developers couldn't reproduce it on our servers but here is a quick workaround.
1. Access your server files using FTP or Cpanel. 2. Navigate to
Problem:
The client is experiencing an issue where the default value from an Elementor form is not available for translation in WPML Translation Editor
Problem: If you're experiencing an issue where the page title appears between the menu and the slide part on your translated pages, Solution: First, ensure that the page options in both the default and translated pages have the same values. If they differ, follow these steps: 1. Navigate to WPML >> Settings >> Custom Fields Translation section. 2. Look for the problematic custom field, such as “title”, and set it to “Copy”. 3. Save the changes. 4. Re-save the default language page to apply the changes to the translated page. For more detailed guidance, check out our documentation on Translating Custom Fields.
Problem: If you're experiencing issues with some texts not being translated when switching to a specified language, even though all texts were translated using the WPML plugin, the problem might be related to the custom tabs Elementor element that is not WPML Translation Editor compatible. Solution: To resolve this issue, we recommend the following steps: 1. Add the following XML configuration to the WPML >> Settings > Custom XML Configuration section:
3. Make a small change in the default language page, then open the secondary language page in the WPML Translation Editor and add the translated template IDs as a translation. This should display the translated content on the frontend. For more details, you can refer to the following documentation:
Problem: The client was unable to synchronize their translated menus. Despite running a full sync, the hierarchy was not updated, and the same lines appeared for syncing again. Solution: 1. We recommended performing a full backup of the site. 2. We instructed the client to delete the translated menus. 3. We advised re-translating the menus using the sync menu option in WPML. 4. To delete a translated menu, we suggested using the language switcher to switch to the secondary language and then delete the menu from there. 5. After deletion, we recommended using the menu sync feature to resync the menus. 6. We provided a link to the UpdraftPlus plugin for backup purposes: https://wordpress.org/plugins/updraftplus/ 7. We shared a screen recording demonstrating the removal and resyncing of the "ny produktkategori" menu for the English language: https://screenpal.com/watch/c0loonVHVCH
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us for further assistance: Contact WPML Support
After making any search, if I change the language, the search criteria disappear, and I return to the store.
How can I, for example, search somthing in Portuguese and, after that, change to English, and the results will appear the same but in English?
Solution:
You need to tell WPML those parameter names by a comma-separated list in WordPress Dashboard > WPML > Languages > Language switcher options > Preserve URL arguments.
Problem: The client is trying to make their store multilingual, translating from English to Dutch. They encountered issues with incorrect margins on the Dutch store, inability to edit pages in Elementor or WordPress, a missing footer in the Dutch version, and the WooCommerce Multilingual plugin not being recognized.
Solution: We checked the issue and found that the shop page was corrupted. We resolved this by creating a new shop page and translating it. We recommend checking if the new translated shop page works correctly. Additionally, we translated the footer template as it was not previously translated. If you're experiencing similar issues: 1. Verify if your shop page is corrupted and consider creating a new one. 2. Translate the new shop page and check its functionality. 3. Ensure that the footer template is translated.
Problem: The client is unable to see the option to set up the "WooCommerce Multilingual & Multicurrency" plugin after installation, which is necessary for making Shop/Category multilingual in conjunction with WPML. Solution: 1. We asked the client to confirm if the plugin was activated after installation. 2. We suggested looking for a setup wizard notification at the top of the admin area to start the configuration process. 3. We recommended checking for compatibility issues by: - Creating a full website backup. - Disabling all plugins except for WPML, its add-ons, and WooCommerce (excluding other WooCommerce add-ons). - Checking if the issue persists. - If the issue is resolved, reactivating plugins one by one to identify the problematic plugin. - If the issue still occurs with non-WPML plugins disabled, switching to a default theme like TwentySeventeen to test for theme-related issues. We advised performing these steps in a staging environment if possible and to inform us of any changes or if the issue is resolved.
Problem: The client is unable to translate the default Divi Countdown Timer module. The strings "Day(s)", "Minute(s)", etc., are not found in the WPML String Translation, and there are inconsistencies in translations across different languages and devices. Solution: 1. Navigate to WPML -> Theme and Plugin Localization. 2. Select the Divi theme. 3. Click on Scan the theme for strings. 4. Go to WPML -> String Translation. 5. Search for the strings you wish to translate. 6. Translate them on the provided sandbox site.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us.
Problem: The client needs to translate the footer widgets. Solution: We recommend going to WPML > String Translation and searching for the text added in the footer widgets. Once found, the client can proceed to translate them. For more detailed instructions, please check out our guide on translating widgets using String Translation.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
