[Resolved] “Not valid” Status for Language Domains in WPML
This thread is resolved. Here is a description of the problem and solution.
Problem: You are configuring WPML to use a different domain per language. The Danish (https://eewto.dk) and Finnish (https://eewto.fi) domains are marked as 'Not valid' in WPML, despite being correctly entered and pointing to the appropriate servers. The Swedish domain (https://wingtsun.se) is working correctly. You've tried various troubleshooting steps including clearing WPML cache and re-checking domain DNS and SSL status. Solution: We have encountered similar issues previously, which were caused by the Hostinger Preview Domain plugin. This plugin is intended for temporary domain use during website development. In your case, you should disable or delete this plugin. You can do this by renaming the plugin folder via file manager or removing it entirely. Disabling the Hostinger Preview Domain plugin should resolve the issue with the domains being marked as 'Not valid'.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum at WPML Support Forum.
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 currently configuring WPML to use a different domain per language. The Danish domain (hidden link) and Finnish domain (hidden link) are marked as 'Not valid', even though they are correctly entered and point to the appropriate servers. The Swedish domain (hidden link) is working correctly. I’ve enabled 'Validate on save' for both non-working domains, but it still returns the error. All domains are properly configured in DNS and accessible via browser. SSL certificates are active and working as expected. I’ve tried clearing WPML cache, re-checking domain DNS and SSL status, saving settings with and without validation enabled, and verifying domain accessibility directly in the browser.
Symptoms:
Domains for Danish and Finnish are marked as 'Not valid' in WPML.
Questions:
Could you please help identify why these domains are showing as invalid?
How can I fix the issue with the domains being marked as 'Not valid'?
Yes, this entry was created based on information we found both from you and other support forums regarding WPML multilingual and multidomain support. This code can be removed, and we’ll be looking forward to your feedback.
The code lines were removed, but the issue remains. When changing the language in the footer, it still redirects to the .fi domain instead of returning to the root domain of wingtsun.se. Also this is changed in backoffice automatically.
I have recently similar case, and it was caused by Hostinger Preview Domain, which is a plugin for "Enable access to the website through a temporary domain while the main domain is not yet configured."
So basically it is for temporary domain use, while the website is in development, so you do not need it In your case, you can disable it, or rename the folder via file manager to disable/ or delete it. Then it should work fine.
I’ve checked both the WordPress back office and the FTP under the modules folder, and I can confirm that the “Hostinger Preview Domain” module is not installed.
Additionally, I’ve observed that the issue persists when selecting a language-specific domain (e.g., .se/dk or .se/fi). In these cases, WPML still overrides the main domain to .fi (the Finnish version), regardless of the selected configuration.
This suggests that the issue is more global and likely tied to WPML itself, rather than the multi-domain setup or domain mapping.
Looking forward to your response.
P.S. From the stakeholder’s perspective, this issue has been ongoing for too long, and we urgently need a working solution. Otherwise, we’ll have to discuss a refund process. We appreciate your support and understanding.
We have had the same issue and reports from clients, it is a known issue, and the solution for now is to disable that plugin, as I have said. If you are not sure how to do it, you can provide me with FTP access and I can do it for you.
Image attached, so you can see the plugin is used on your website.