If this solution does not apply to your case, or if it seems outdated, 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.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I’m trying to see the WooCommerce reviews translated on the frontend. Here is the link to the page where the issue can be seen: hidden link
Symptoms:
Reviews are not translated in the frontend; instead, they are displayed in their original language.
Questions:
Why are the reviews not translated in the frontend?
How can I fix the problem of reviews not being translated?
The Duplicator plugin we usually use is not working on Kinsta, and WP All in One Migration is blocked. To test this locally, we’ll need a manual dump of both the FTP files and the database.
As it seems, Migrate Guru only supports migrations from host to host and doesn’t provide file dumps.
Thank you! I’ve received the files, and everything looks correct. I’ll proceed with the deployment now and will keep you updated if I come across anything.
Thank you for your patience. It took me a bit of time to get the package running as there were some missing elements.
I’ve deployed the package and can confirm that the issue does not occur on my localhost with the same plugin and theme configuration.
The only difference is the absence of caching constants in the wp-config.php file. Based on this, I suspect the issue might be caching-related. I recommend testing this on a cloned site without caching to verify.
I checked with my host but there is no server caching active on our staging website and wp rocket is disabled. Is there any other (woocommerce / wpml) caching that we can empty?
Your IP is routed through Cloudflare. I recommend ensuring they test this properly. If you have access, try disabling the CDN and caching in Cloudflare temporarily to see if that resolves the issue.