New address for site recognized, but URLs are the same

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are experiencing issues accessing the Translation management page on your staging site. The page appears blank, and you receive a message indicating that the site seems to have moved, although the URLs are the same. Additionally, there is an error in the admin bar about needing to map languages, but no languages are loaded for mapping.
Solution:
We resolved the issue by setting the site as a copy, which made the Translation management page available again. To connect your sites and share translation memory and credits, we recommend following the steps outlined in our documentation on Automatic Translation Subscription for Multiple Sites.

If this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. For further assistance, you can also 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.

Tagged: Documentation request

This topic contains 0 replies, has 0 voices.

Last updated by Bruno Kos 2 weeks, 3 days ago.

Assisted by: Bruno Kos.

Author	Posts
April 8, 2025 at 10:11 am #16908245
markusN-7	Background of the issue: I am trying to replicate behavior for another ticket and access the Translation management page on the staging site. Symptoms: I expected to see the normal Translation management page without errors and warnings. Instead, I got a message indicating the page seems to be moved to another site, but the URLs are the same. The Translation management page was blank, and after reloading, I received the same message. Additionally, there is an error in the admin bar indicating I need to map my languages, but no languages are loaded in the input for changing the mappings. Questions: Why is the Translation management page blank? Why am I receiving a message that the site appears to be moved when the URLs are the same? How can I resolve the error about mapping languages when no languages are loaded?
April 8, 2025 at 11:13 am #16908744
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	I marked your next reply as private so that you can safely add credentials. If possible provide me logins for both sites (production and staging, if the issue happens in both). You can create a custom admin user with admin@example.com email.
April 8, 2025 at 1:15 pm #16909599
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Can you temporarily disable Authentication Code on the staging so I could login without system asking for it?
April 8, 2025 at 1:51 pm #16909718
markusN-7	I'm sorry, 2fa is disabed now
April 9, 2025 at 9:04 am #16912019
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	I set it as a copy and the translation management is now available. You can connect the sites like this now: https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/#how-to-connect-your-sites so that the translation memory and credits are shared.
April 14, 2025 at 10:12 am #16928226
markusN-7	Thanks a lot, it is working now. Did you do anything special? I tried setting the site as a copy several times, but with no success.
April 14, 2025 at 11:34 am #16929025
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	That's all I did, maybe there was some browser caching involved on your end which prevented this from working properly.