This site has moved to a new location

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: ATE

This topic contains 24 replies, has 2 voices.

Last updated by Alejandro 1 year, 11 months ago.

Assisted by: Alejandro.

Author	Posts
August 16, 2023 at 5:55 pm #14240493
burcuK-2	I am sorry but the same error message is on admin page after a new staging commit from production. New screenshot is attached.
August 17, 2023 at 8:11 am #14243503
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	Are you migrating the database from production to staging, by any chance? and if you are, are you using a specific way to do this? I'm asking this because i've been trying to recreate this problem on my end a few times already and i use a simple plugin like all in one migration, and i always get the correct outcome, no matter how much i try to recreate your problem, on my case it always works so there must be something i'm missing here. Would it be possible for you to maybe record yourself while trying to migrate the site from production to staging? Afterwards, you can apply the same workaround i mentioned earlier, but maybe this time only remove one entry: otgs_wpml_tm_ate_cloned_site_lock If this removes the banner, then try to see if you can migrate again and then translate some content. Let me know please and sorry for all this migration issue! i'm going to make sure this testing will be worth the while! Regards.
August 17, 2023 at 8:21 am #14243609
burcuK-2	Hello again and thanks for the answer. Migration is done via All-In-One WP Migration plugins's backup files. Backup procedure on the plugin is default. No extra settings and exclulions. Full production site backup. File size limitation is removed via paid extension. Then we move the backup file to the staging site hosting container via terminal and / or FTP. After that we just recover production site backup file on staging with default settings. Due to using multiple steps on separate tools, I would rather not record it but I can provide additional information if you need. Regarding "the same workaround": Shall I commence it on production or staging?
August 17, 2023 at 8:49 am #14243903
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	The workaround is always done on the site that has the "blocking" banner, so in here it would be the staging site. Thanks for the procedure, if you use All in One Migration then it's practically the same procedure i tested and at this point i'll test a few other scenarios to see if i manage to recreate the problem. Try y workaround and let me know if it works for you.
August 17, 2023 at 9:28 am #14244273
burcuK-2	I have done the instructions on your previous post: https://wpml.org/forums/topic/this-site-has-moved-to-a-new-location-7/#post-14198355 except the removal of db table rows but one. No joy. Same error message is on the admin panel.
August 17, 2023 at 9:40 am #14244491
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	Ok, in this case please use the same exact workaround as before and let me know so i make the changes on my end to have the problem sorted. I'm still running a few tests on my own but i think i know how you managed to recreate the problem, my last test will tell and i'll be able to send this problem to our dev team so we can have it sorted.
August 17, 2023 at 9:43 am #14244503
burcuK-2	Then I will delete all three rows from the database now. Previously, I have deleted only one. ... Deleted three rows from the query you provided. Now admin home page shows no warning about WPML.
August 17, 2023 at 1:25 pm #14246615
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	Hm, i can see that unlike with the other site, the translation memory and everything else was already ok, even after the change you made in the database which in theory had to "reset" everything. Can you check that the translations are there in the translation editor, please?
August 17, 2023 at 4:57 pm #14248001
burcuK-2	Translations are there in their place. But what's different for this domain is that we have not used automatic translation yet. Only main service pages, contact, about and homepage have been translated but manually. We will start automatic translations with the blog posts but not yet.
August 18, 2023 at 8:58 am #14250873
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	Alright, then everything's set. For now, i'd recommend that you use the "yes" option instead of the "no" option, so you treat the sites as a copy. that way the "old" site that you're moving won't be blocked and can be reused in the past. If you use the workaround that i mentioned, and you lose the translations, make sure you link the site that does have the translation memory with the "new" one you used the workaround in. you can do so by following this guide: https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/ Regards.