[Resolved] address conflict on development website
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is setting up French translations on their development website and encountered an issue where WPML is recognizing an Amazon alias domain instead of the actual domain (2024.hpac.ca) registered for translations. Solution: 1. Ensure that the site URL and the site key URL protocols match (both should use https). 2. Delete the existing development site entry from the WPML account and create a new key that matches the exact URL format used by WordPress, including the protocol (https://2024.hpac.ca). 3. In the WordPress admin, navigate to Plugins → Add New → Commercial tab, unregister WPML if available, and then register WPML with the newly generated key. 4. Avoid using the migration wizard if both domains point to the same WordPress install/server. Instead, select "I just logged in from a secondary domain" as detailed in the documentation: Using Advanced Translation Editor when you move or use a copy of your site. 5. If the button is not visible and updating WPML is not an option, navigate to WPML → Support → Troubleshooting and click on Force-enable WPML’s Advanced Translation Editor.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also 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. 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.
We would be doing FR translations for our staging / development website at 2024.hpac.ca .
This website is registered as a development website on our WPML account.
- hidden link
When we access though the WPML Translation Management page on the website, we get this notification.
- hidden link
The development website is hosted at Amazon, but the WPML notification seems to say that the new address of the website is the Amazon alias domain - hidden link - though, the domain 2024.hpac.ca is the actual active domain.
Can you please check on this and provide us steps / details on how we can set on WPML that the active link of the development is 2024.hpac.ca so that we can proceed on setting up the translations?
I was guided by the support AI and I'm now at this dialogue page.
- hidden link
Clicking the link did not provide any migration code and I was only redirected to a page which displayed the initial new address for this site detected.
- hidden link
At this point, the support AI recommended a human support.
To ensure the quickest and most accurate support, please provide your debug information so I can look at some of your configurations. We have an excellent article on how to locate it here: https://wpml.org/faq/provide-debug-information-faster-support/.
In Settings → General, the WordPress Address (URL) and Site Address (URL) are authoritative for what WordPress thinks the site URL is; if either is set to the EC2 alias (or being overridden by constants), WPML can legitimately “detect” that other address. In Settings → General, what are the exact values of WordPress Address (URL) and Site Address (URL)?
Is it possible for you to set them to 2024.hpac.ca there? Or your setup does not allow it? ❌ Please make a full website backup before proceeding ❌
I think that the migration code advice was not right, you are not actually migrating a site as far as I understand. WPML should handle sites with two domains pointing to the same sites.
I noted that the URL in the site settings and the URL for the registered site key don't match. They have different protocols: http (site) and https (key).
I suggest trying the following:
❌ Please make a full website backup before proceeding ❌
1. Fix the site URL or the site key URL so they match.
2. Then go to WPML.org → Account → Sites and delete the existing dev site entry for this install and create a new key for the exact URL format WordPress uses (must match hidden link exactly, including the protocol).
3. In the WordPress admin: Plugins → Add New → Commercial tab → Unregister WPML (if available) → Register WPML with the newly generated key.
