Problem: The client reported that after translating their shop page from Portuguese to English using WPML, no products or content were displayed on the English version of the shop page.
Solution: We identified that the client needed to install the WooCommerce Multilingual addon to properly display translated products on the shop page. We advised the client to install this addon without deleting the existing translations, as the addon would automatically correct the issue. After installation, the client noticed that all products, including those not yet translated, were showing and some items appeared duplicated. We checked and completed the WooCommerce Multilingual setup, which initially didn't display due to a conflict with another plugin blocking the setup notice. Once the setup was completed and the conflicting plugin was addressed, the shop page displayed content correctly.
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 issues persist, please open a new support ticket.
Problem: After activating and configuring WPML on the client's website, all pages were redirecting to a 404 error page. Solution: We recommend taking the following steps to resolve the issue: 1. Ensure you have a full backup of your website and database. 2. Increase the 'WP Memory Limit' to at least 128MB, preferably 256MB. You can do this by adding the following code to your wp-config.php file:
Make sure to add these lines before the 'That's all, stop editing! Happy publishing.' line. 3. Deactivate all plugins except for WPML and its addons to check if the issue persists. 4. Reactivate each plugin one by one, checking your website after each activation to identify any plugin that may be causing a conflict. 5. If the problem continues, repeat the steps using a default WordPress theme, such as Twenty Twenty-One or Twenty Twenty-Three.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem 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:
When we enable the plugin WPML String Translation version 3.2.8 we get a critical error and cannot see the plugin's details in the installed plugins page.
The debug log file shows the following error:
[30-Nov-2023 14:59:56 UTC] PHP Fatal error: Uncaught ValueError: Missing format specifier at end of string in ........./wp-admin/includes/plugin-install.php:676
Stack trace:
#0 ........./wp-admin/includes/plugin-install.php(676): printf()
#1 ........./wp-includes/class-wp-hook.php(324): install_plugin_information()
#2 ........./wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 ........./wp-includes/plugin.php(517): WP_Hook->do_action()
#4 ........./wp-admin/plugin-install.php(82): do_action()
#5 {main}
thrown in ........./wp-admin/includes/plugin-install.php on line 676
Solution:
The line mentioned in the error outputs the string "%s ago" which was translated incorrectly in String Translation. Fixing the translation of the %s placeholder resolved the issue.
Problem: The client needed to translate a link on a button to English, but encountered a message indicating that the string could not be translated automatically because it was not in the site's default language. Solution: We recommended the following steps: 1. Go to WPML String translations and scroll to the bottom, then click on "Translate texts in admin screens »". 2. Search for the ID of the theme option button URL, which in this case is
"btn_link_v1"
. 3. Click on "Add to String Translation" button to add it to the string translation list. 4. Return to WPML String Translation and switch the default language as previously indicated. For more detailed instructions, please refer to our documentation on Finding strings that don’t appear on the String Translation page. We have added the string for the client, and the website should now display the translation correctly.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
Problem:
"An error of type E_ERROR was caused in line 3937"
There was a conflict between WPML and the latest version of Google Site Kit (1.106)
Solution:
On the moment, the workaround was to downgrade to Google Site Kit 1.105, but a few days after we released WPML 4.6.5 which solved the issue. Please update WPML.
