Migrations between environments with WP Migrate DB Pro

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-
-	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-

Supporter timezone: America/Bahia (GMT-03:00)

This topic contains 13 replies, has 2 voices.

Last updated by Marcos Vinicios Barreto 2 years, 9 months ago.

Assisted by: Marcos Vinicios Barreto.

Author	Posts
March 30, 2022 at 12:55 pm #10911559
davidC-175	Hey there, I have a problem. We are hosted on WP Engine and have three environments (PRD - production.cloudtalk.io; STG - staging.cloudtalk.io and DEV - devcloudtalk.wpengine.com). We would like to make changes on Staging env and then on Production run PULL to get changes live. In other situations, we should occasionally run PULL on DEV env to get an actual version for development purposes. The problem seems to be with WPML, we have all three envs on different domains and all of them are registered on WPML. PRD is registered as production WPML, STG, and DEV as development WPML. However, we have struggled with PULLs. After a PULL on DEV (to get STG) - the WPML warning about "site moved or copied. Which I definitely don't want to click after every migration. And the second part of the problem - after a PULL on PRD (to get STG) - the WPML warning shows but the even bigger problem - production WPML is now registered as development on WPML. I really need to fix this asap. Is there any chance to get rid of migrating WPML licenses data to prevent this? I'd really appreciate your help. I am pretty desperate. :-/ Thank you very much and have a nice day.
March 30, 2022 at 10:15 pm #10915031
Marcos Vinicios Barreto	Hello, Thank you for contacting our support service. I recommend you to review these instructions: https://wpml.org/faq/automatic-wpml-registration-using-php-for-easy-moves-between-production-development-and-staging/ Please, let me know if it helps. Have a nice day.
April 4, 2022 at 2:35 pm #10945431
davidC-175	Hello, I'm reopening this ticket due to the continuous state of still-returning warning with "site moved or copied". I set up OTGS_INSTALLER_SITE_KEY_WPML in wp-config on all three envs with their proper keys. However, the warning keeps returning paralyzing our translation management and changes migrations. Even when on STG is never migrated from any other the warning returns. Even when I pull changes on PRD from STG and on DEV from STG ... It really doesn't matter what we are doing ... the warning becoming to be a real nightmare for us. I would really appreciate your help asap.
April 5, 2022 at 5:11 pm #10957083
Marcos Vinicios Barreto	Hello, Thank you for the updates. I am consulting our second level support team for a more details regarding this issue. I will update you here as soon as I have some more details regarding it. Thank you for your continued patience and understanding. Have a nice day.
April 7, 2022 at 2:47 pm #10974147
Marcos Vinicios Barreto	Hello, Thank you for your patience while waited. Please, try the following procedures: 1 - As regarding the key registration issue, unregister your websites and register them according these instructions: https://wpml.org/faq/automatic-wpml-registration-using-php-for-easy-moves-between-production-development-and-staging/. The point here is to unregister them and make sure sure they are registered with the key defined in wp-config.php file. Just adding the key as constant in this file, without unregistering the site first won't make it work properly. Please, make sure to not delete those keys in your wpml.org account. 2 - As regarding the ATE notice regarding site moved or copied, ATE stores the website domains in order to track when they change, the registration key wont prevent it. So, the noticed is required and we don't have any way of preventing it for now. You can sugest a feature to prevent it at: https://wpml.org/suggest-a-new-feature-for-wpml/ Hope it helps, have a nice day.
April 13, 2022 at 12:29 pm #11013155
davidC-175	Hello, I still stuck. 🙁 Here is what I did: 1) I commented out WPML keys in wp-config.php at all 3 envs. And cleared cache. 2) I navigated into Plugins - Add new - Commercial and there I unregistered site. Did on all 3 envs. 3) I deleted all the keys in WPML admin. And cleared cache. 4) I created a new key and added him into the WPML key in wp-config.php and uncommented it. Did on all 3 envs. And cleared cache. 5) I checked in WordPress that new key is loading from wp-config.php. 6) Site moved/copied alert occurs on two envs. I set moved and cleared the cache. It worked for two hours. But now the alert still returns - and turns me very mad. What did I wrong? I think I did everything perfectly. How could this be happening?
April 14, 2022 at 5:15 pm #11023805
Marcos Vinicios Barreto	Hello, Thank you for the updates. I forwarded these points to our second level support so a possible escalation could be considered. I will update you here as soon as I have some more details regarding it. Thank you for your continued patience and understanding. Have a nice day.
April 18, 2022 at 4:37 pm #11039575
Marcos Vinicios Barreto	Hello, Thank you for your continued patience. I got some more details from our second level support team and a possible explanation for the 'site move/copied' notice is back again should be due some action in the database. You mentioned it happens around 2 hours after you click to dismiss it. Can you please, confirm if you migrate the database in this period? If so, then it is expected. Thank you for your collaboration. Have a nice day.
April 19, 2022 at 2:24 pm #11046679
davidC-175	Yes, we had to try the migrations and if it works. So migrations contain particular database tables, plugins, media etc. So after the setup - yes the migration took place. But I don't understand how it should be expected behavior if this might be exactly the right fix for this problem. Even here is explained "If you are frequently moving the database between production, development, and staging" -- https://wpml.org/faq/automatic-wpml-registration-using-php-for-easy-moves-between-production-development-and-staging/ So it should work just for this case of database migrations. 🙂
April 21, 2022 at 1:23 am #11059905
Marcos Vinicios Barreto	Hello, Thank you for the updates. I forwarded your updates to our second level support, so we can consider an escalation for a complete investigation. I will update you here on the progress of your request. Thank you for your continued patience and understanding. Have a nice day.
April 22, 2022 at 4:48 pm #11080401
Marcos Vinicios Barreto	Hello, Thank you for your patience while waiting. This issue is now escalated to our second level support for a detailed investigation. I will update you here as soon as I have some more details on the issue resolution progress. Thank you for your understanding. Have a nice day.
May 2, 2022 at 6:38 am #11130721
davidC-175	Hi, it's been quite a while. Any update on this issue?
May 3, 2022 at 4:03 pm #11142459
Marcos Vinicios Barreto	Hello, Thank you for the updates. I've just checked our issue tracker and unfortunately we still don't have any workaround for that. I pingged our supporters in order to have a resolution for that. I will update you here as soon as I have some more details. Thank you for your continued patience and understanding. Have a nice day.