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?
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.
I followed the steps mentioned above, but the first and second solutions didn’t work. However, after disabling the CDN and copying WPML to the old domain (as enabling the CDN switches to a new domain), it worked. Could the issue be related to the CDN, or is it a matter of the old domain versus the new domain?
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+01:00)
Just to clarify, when you say enabling the CDN switches to a new domain, are you referring to serving static content (like images, CSS, and JavaScript) from a different domain or subdomain, while the main website domain remains the same?
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+01:00)
Can you perhaps show me the settings as you have them in CDN?
Or perhaps even record a video using tools such as hidden link to show me how this whole process works in your case?
Because in general, enabling a CDN should not force an entire website to switch to a new domain. CDNs are designed to work seamlessly with your existing domain, typically by integrating with DNS settings. CDNs typically act as a reverse proxy, meaning they cache and serve content from the origin server while keeping the original domain intact.
We conducted the following experiments: when switching the domain without enabling the CDN, WPML worked fine. However, when the CDN was enabled on the new domain, the issue occurred. Therefore, I believe the problem is related to the CDN. I’m uploading some settings along with this reply.
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+01:00)
I am checking this with our 2nd tier, at first it may seem that this could be caused by CDN Cache Issue or maybe CDN and API Conflicts. WPML's ATE connects to its remote translation servers using API requests, if the CDN interferes with these requests (e.g., blocks them or redirects them incorrectly), it can break the connection.
But these are all just guesses as we have no other reports of this kind yet, so I am trying to get some information from our 2nd tier on this.
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+01:00)
Can you gather this information for us as it would help us understand what is behind this?
### **1. CDN Cache Issue**
**Cause:** CDNs cache files like JavaScript and CSS to improve performance. However, if these cached files are outdated or incomplete, WPML’s ATE might fail to load properly.
**How to Check:**
- Look for errors in your browser’s developer console (F12 > Console tab). Missing or outdated files often show as 404 errors or failed requests.
- If you recently updated WPML or your website, the CDN might still be serving older versions of critical files.
---
### **2. Browser User-Agent Blocked**
**Cause:** Some CDNs use strict security rules that block certain browser User-Agent strings. WPML’s ATE might use a User-Agent that is inadvertently blocked.
**How to Check:**
- Inspect the logs in your CDN dashboard for any blocked requests.
- Use your browser’s developer console (Network tab) to see if requests from the WPML ATE are being rejected or flagged as suspicious.
---
### **3. HTTPS or Mixed Content Issues**
**Cause:** If your site is using HTTPS but some resources are still served over HTTP, or if HTTPS is not fully configured with the CDN, required files might not load.
**How to Check:**
- Open the browser console and look for "Mixed Content" warnings. These indicate that some resources are being loaded insecurely.
- Verify your site's SSL configuration and whether HTTPS is properly enforced.
---
### **4. Incorrect CDN Configuration for WPML**
**Cause:** Certain optimizations in the CDN, such as minification, concatenation, or aggressive compression, may interfere with the JavaScript files required by WPML’s ATE.
**How to Check:**
- In the browser console, check for JavaScript errors. Files that fail to execute or are corrupted often indicate issues with CDN optimizations.
- Compare the loaded file sizes against their original sizes in the Network tab to identify unexpected compression or modifications.
---
### **5. Cross-Origin Resource Sharing (CORS) Problems**
**Cause:** WPML’s ATE loads resources across domains, which requires proper Cross-Origin Resource Sharing (CORS) headers. If these headers are missing or misconfigured, resources may fail to load.
**How to Check:**
- Look for CORS-related errors in the browser console. Common messages include "No 'Access-Control-Allow-Origin' header is present."
- Inspect the response headers for problematic requests in the Network tab.
---
### **6. CDN and API Conflicts**
**Cause:** WPML’s ATE communicates with its servers through API calls. If the CDN blocks these API requests or redirects them incorrectly, the ATE will fail to connect.
**How to Check:**
- Use the browser’s developer console (Network tab) to check if requests to `hidden link` or `hidden link` are blocked or redirected.
- Check the HTTP response codes for these API requests—codes like 403 (Forbidden) or 404 (Not Found) indicate issues.
---
### **7. DNS Propagation Issues**
**Cause:** After switching to a new domain or making changes to DNS settings, the CDN might serve inconsistent data if the DNS has not fully propagated.
**How to Check:**
- Use tools like [DNS Checker](hidden link) to confirm whether DNS changes have propagated globally.
- Check if different locations (or devices) load the website differently.
---
### **8. Browser Compatibility Issues**
**Cause:** If the browser receives incompatible or outdated files from the CDN, WPML’s ATE might not function correctly.
**How to Check:**
- Test the website in multiple browsers or in incognito mode to rule out browser-specific issues.
- Use the browser console to identify specific errors, such as files failing to load or unsupported features.
---
### **Next Steps for Diagnosing the Issue**
1. Use the browser’s developer tools (F12) to check for errors in the Console or Network tabs. Look for issues like blocked requests, 404 errors, mixed content warnings, or CORS issues.
2. Review your CDN’s logs or dashboard for blocked requests or unusual behavior.
3. Check whether the problem persists when accessing the site from a different browser, device, or network.
If you’re unable to identify the root cause, your hosting provider or CDN support team can assist in analyzing these issues further. Let us know if you need additional guidance!
