Home›Support›English Support›[Resolved] Error in WP Dasboard - saying my live site is a duplicate of a non existant domain
[Resolved] Error in WP Dasboard - saying my live site is a duplicate of a non existant domain
This thread is resolved. Here is a description of the problem and solution.
Problem: The client encountered a WPML message in their WordPress dashboard asking if their main site laspeziaguide.com is a duplicate of a non-existent domain wpml.wpml.laspeziaguide.com. This message was confusing as the domain mentioned does not exist and the client had not recently created a staging site with that URL. Solution: We determined that the message was not generated by WPML but possibly by other plugins (Admin Site Enhancements or Unlimited Elements for Elementor) that check for a license. The client should verify which plugin generated the notice by following any available links in the message for more information. If the issue persists, the client should contact the support for those plugins. Additionally, we resolved the issue from our side by adjusting the organization IDs and merging them in our system, ensuring the client can continue using the Pay as you go system for translations. To prevent future issues, follow the steps outlined in the WPML documentation on handling site copies: Using Advanced Translation Editor when you move or use a copy of your site.
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 logged in to my WordPress dashboard and encountered a WPML message regarding site duplication. I have two staging subdomains: staging.laspeziaguide.com and wpml.laspeziaguide.com, which I recently provided to WPML for troubleshooting an issue.
The domain wpml.wpml.laspeziaguide.com does not exist.
Symptoms:
I received a WPML message asking if laspeziaguide.com is a duplicate of wpml.wpml.laspeziaguide.com, which does not exist. The message also asked if laspeziaguide.com is the new home of wpml.wpml.laspeziaguide.com or if it is a new website.
Questions:
Why is WPML asking if laspeziaguide.com is a duplicate of a non-existent domain?
How should I proceed if laspeziaguide.com is not a duplicate, not the new home, and not a new site?
Hello!
Before one of my colleagues take your case, I wanted to drop-in here and respond in hopes that I can help you with this case.
The message that you are getting does not appear to be coming from WPML.
As far as I can see, there are two plugins - Admin Site Enchancements and Unlimited Elements for Elementor - which check for a license, and this message may be coming from one (or from both) of them.
If you have recently created a staging site, it is better to resolve the warning and have the license activated only on the site that you are using.
Perhaps you should contact the mentioned plugins for further guidance on how this can be done.
From my personal point of view, I think that you should select the option that migrates the license to your domain - but I am not familiar entirely with those plugins and I cannot say exactly.
I read that as though WPML is placing the two plugins into safe mode (which I don't believe they actually are).
Our main/live site is laspeziaguide.com
My issue is I have not recently created a staging site, maybe a couple months ago we created wpml.laspeziaguide.com BUT, NEVER have we created wpml.wpml.laspeziaguide.com
It does not exist anywhere on our server.
Also, my bigger concern is that it is asking if our live site is a duplicate of something that does not exist...
WPML itself would not embed a URL into your site such as wpml.wpml, therefore I am not sure where this is being pulled from.
When I review your debug information shared with us I can see that the database items are correctly set as follows:
SiteURL hidden link
HomeURL hidden link
As the warning notice does not look like something generated by WPML, I cannot say with confidence what is the best option here.
Which plugin is generating this notice? If you click on "Unsure what to do? Read More" where does that take you to? Hopefully this will lead us to a documentation and let us know which plugin is bringing this notice up.
When I log into our WordPress dashboard (just did it now), I get a message that currently looks like a WPML message.
After taking the screenshot of the original one the other day, I must have closed it down, and now this appears (see attached).
The 2 plugins that it mentioned are 100% active and not in any type of safe mode.
It is making the same statement as the other:
Looks like this site was previously at hidden link and now it’s at hidden link.
This is our live site: hidden link
And this does not exist and has never existed, especially "as our current site" as the message is basically stating: hidden link
In the past, I have made a staging site from hidden link and created: hidden link (and it still exists)
BUT never this: hidden link
Also, as you said, the debug states the DB items are correct:
SiteURL hidden link
HomeURL hidden link
So, I cannot do any translations until I select an option here - and neither is correct.
It is not a copy, and I haven't updated the site to a new one recently.
Thank you for sharing this. Yes, this is indeed a WPML notice.
I’ve reviewed your account on our end, and everything appears to be in order.
The easiest way to remove the notice is to select the option indicating this is a “copy,” then proceed without connecting the sites.
That said, I’d like to test this myself—if it creates a separate instance, I’ll be able to resolve it on our backend and make sure your translations are functioning correctly.
I was able to remove the warning and also merge the site to the correct ATE account so you should be able to use the Pay as you go system and resume your translations as expected.
