Translation Page Error: Browser Not Supported

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	8:00 – 13:00	9:00 – 13:00	9:00 – 13:00	8:00 – 12:00	8:00 – 12:00	-
-	14:00 – 17:00	14:00 – 18:00	14:00 – 18:00	13:00 – 17:00	13:00 – 17:00	-

Supporter timezone: Europe/Zagreb (GMT+01:00)

Tagged: ATE

This topic contains 0 replies, has 0 voices.

Last updated by Bruno Kos 1 day, 2 hours ago.

Assisted by: Bruno Kos.

Author	Posts
January 3, 2025 at 8:50 am
nijunW	Background of the issue: I am trying to access the WPML translation editor to translate WooCommerce products. The website domain has been changed recently, and I have re-registered WPML and replaced the key accordingly. WPML plugins are all up-to-date. Symptoms: I received an error message stating 'Your browser is not supported. Please try Chrome browser,' even though I am using a Chrome browser. Questions: Why am I receiving a browser not supported error when using Chrome? Could the recent domain change affect the WPML translation editor?
January 3, 2025 at 9:23 am
January 3, 2025 at 1:28 pm #16561523
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	I am checking this with our 2nd tier and will keep you posted.
January 7, 2025 at 7:04 am #16568085
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	Can you please try the following: 1. Deactivate all plugins except WPML and check if the issue persists. This will help identify if there is a conflict with other plugins. 2. Switch your theme to a default WordPress theme like Twenty Twenty and test again. This will help determine if the issue is related to your current theme. 3. Clear the CDN cache or temporarily disable the CDN and check if the issue is resolved. This will help identify if the caching mechanism is causing the problem. Let me know the results of these steps for further troubleshooting.