Home›Support›English Support›[Resolved] Setting "A different domain per language" stopped working after update
[Resolved] Setting "A different domain per language" stopped working after update
This thread is resolved. Here is a description of the problem and solution.
Problem: The client updated WordPress to version 6.7 and all WPML plugins to the latest versions. However, they encountered an issue where they could not switch the frontend language to German (DE) by clicking on the DE flag in the main menu. The domain for the German language was incorrectly redirecting to the main domain. Solution: We first ensured that the client was using the latest WPML version by advising them to update their WPML plugin and add-ons to version 4.6.14. We then guided the client to check their domain and 'A different domain per language' setup according to our guide. Further troubleshooting steps included: - Synchronizing posts taxonomies - Clearing the cache in WPML - Resaving the permalink structure Upon deeper investigation, it was found that the issue was due to a server-level redirection, likely configured in the LiteSpeed server settings or the hosting control panel. We recommended checking the LiteSpeed server configuration, hosting control panel redirects, and DNS settings for the domain. If these steps do not resolve the issue, we advised contacting the hosting provider for further assistance.
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 the problem persists, 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 updated WordPress to version 6.7 and all WPML plugins to the latest versions, which I downloaded from your site as advised in an email. The site I need help with is hidden link. It was set up with a different domain for the DE language before.
Symptoms:
I can't change the frontend language to DE by clicking on the DE flag in the main menu anymore.
Questions:
Can you help with the issue of changing the frontend language to DE?
Is there a known issue with 'A different domain per language' after the update?
While one of my teammates takes care of your ticket, I will provide you with the first debugging steps.
I noticed that you are still using WPML 4.6.13. Please update your WPML plugin and add-ons to the latest version, 4.6.14, to benefit from the latest bug fixes and improvements. This may not necessarily resolve your problem; however, we need to work on the latest code to troubleshoot the issue best.
You can check the latest released versions under "My Account -> Downloads" on this site. Instructions to update can be found here: http://wpml.org/faq/install-wpml/
If you do not see the updates, you might need to click the Check for updates button in the Plugins → Add New Plugin → Commercial tab.
Please remember to backup your database before you proceed.
Let us know if the issue persists after an update has been done.
What I did. I downloaded all 3 plugins from your website, latest version under Manual download. FTPd to server, deleted all 3 folders from /wp-content/plugins/ and uploaded the downloaded, latest versions.
I can give you access to the /wp-admin/ if you need.
Hello Urban,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
I've taken over this ticket and would be happy to assist you further in this matter.
Upon reviewing your site, I noticed that the domain for the German language is incorrectly redirecting to the main domain. I tried identifying the cause of the redirection, but the redirect data is missing in the developer console.
If the other language domain is configured correctly, this redirection shouldn’t occur. on trying to access the domain, the default language page should appear, but without any redirection. Could you please review this guide and double-check the configuration to ensure everything is set up properly?
If the domain and the different domain per language setup are configured correctly but the issue still persists, please try the following steps.
- Please go to WPML > Support > Troubleshooting
- Click on the following buttons:
-- Synchronize posts taxonomies [Select the post type from the dropdown and then click the button]
-- Clear the cache in WPML
-- Assign translation status to duplicated content
-- Set language information
-- Fix post-type assignment for translations
-- Update domain name in language switcher settings
- Once done, go to "Settings > Permalinks" and resave the permalink structure, ensuring the Plain structure is selected.
- Clear the caches from your site and browser and check again.
Please try and let me know how it goes. I'll be happy to help if you need further assistance in this matter.
The DE domain was working before the updates, I check this after each plugin/core update. I made a screenshot of the setup in attachment. The DE domain hidden link is "Valid" when I save the settings.
I also checked DNS settings for this domain, everything looks OK.
I still don't know what is wrong with the plugin versions 🙁 I uploaded via FTP the latest versions, readme.txt files also say so, but in Plugins and Commercial tab it says I have pre-last ones. What is up with that?
Thank you for confirming that the different domains per language setting is configured correctly. Please note that with the latest version of WPML, we haven’t received any reports of issues related to this setup. Therefore, it’s likely that the issue is related to a specific configuration on your site. Could you please also confirm if you have completed the troubleshooting steps I shared in my previous response?
If the issue persists even after that, a closer inspection will be required to understand the root cause of the issue.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. You will find the needed fields below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please backup site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Thank you for sharing the access. I've thoroughly checked everything and would like to provide you with a detailed update on this issue.
What I’ve Done So Far:
1. Analyzed HTTP Headers:
- I inspected the HTTP response headers using tools like `curl` to understand the nature of the redirect.
- The results confirmed that the redirection is a 301 (Moved Permanently), set at the server level, with the `Location` header pointing to `hidden link`.
2. Ruled Out WordPress Core and Plugins:
- Despite enabling full debug logging in WordPress (`WP_DEBUG`, `WP_DEBUG_LOG`, and `WP_DEBUG_DISPLAY`), no errors or redirection-related logs were generated.
- I also used filters like `wp_redirect` to capture potential WordPress-based redirects, but no data related to the redirect appeared, which suggests that the redirection occurs before WordPress is executed.
3. Checked LiteSpeed Server and Cache:
- Based on the `LiteSpeed` server header in the Browser developer tool, I suspect that the redirection may be configured at the server level or within LiteSpeed’s cache.
- Cache interference was also tested by removing caches and temporarily disabling the LiteSpeed cache.
4. Reviewed `.htaccess` File:
- I checked by renaming the `.htaccess` file to ensure no redirection rules (e.g., `Redirect` or `RewriteRule`) were added.
Findings So Far
- The redirection is confirmed to be a server-level configuration, likely originating from:
- LiteSpeed server rules (e.g., a rewrite rule or cache directive).
- Hosting panel redirection settings.
- Domain registrar settings for forwarding or domain aliasing.
- WordPress and its plugins (including WPML) do not appear to be the cause of this redirection. This is evident because:
- No debug logs were generated.
- No WordPress hooks, such as `wp_redirect`, were triggered.
To resolve this issue, I recommend the following steps:
1. Check LiteSpeed Server Configuration:
- Review the LiteSpeed WebAdmin console or server configuration files (which are named `lsws.conf`) for rewrite rules or redirection settings.
2. Check Hosting Control Panel Redirects:
- Log into the hosting control panel (e.g., cPanel, Plesk) and check for domain redirects or forwarding rules under the "Redirects" or "Domain Settings" section.
3. Inspect DNS Configuration:
- Access the DNS settings for `freizeitparks-strauss.at` via your domain registrar and confirm:
- No URL forwarding rules are pointing to `hidden link`.
- The DNS A and CNAME records are correctly set.
If the steps outlined above do not uncover or resolve the source of the issue, it would be best to reach out to your hosting provider. They have access to server-level tools that can analyze and diagnose redirects more thoroughly. Their insights can help identify the exact cause of the redirection and provide guidance on implementing a solution effectively.
I hope you can understand. If you have any other questions or need help, feel free to let me know. I'll be happy to help.
Prosenjit, thank you so much for a detailed analysis. Meanwhile I found out that the hosting company got merged with another one and all the sites were migrated to their servers. Looks like they made a mistake in that procedure.
And the control panel I was checking domain configuration wasn't active and relevant at all :S
Let me first find out what the actual setup is now and try to fix the problem. I will get back here and let you know if it is fixed.
