Last year, we had an issue using WP Migrate when PUSHING development to production (https://wpml.org/forums/topic/migrated-site-and-now-seeing-an-error/) and a supporter helped me fix production, but the development site is still showing the message, "Site Moved or Copied - Action Required" and will not clear. We are working on the second phase of our redesign and will need to push development to production again, but I'm concerned that it the same issue as before will happen again.
1. How can we clear this message on development?
2. To avoid any issues when the time comes, can we simply uncheck all WPML tables and any relevant options (WP options) prior to pushing? If I make any translations on development, I assume they get saved in our account so I would just need to sync them on production after the push.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
the banner you're seeing is happening because you moved a site from "domain a" to "domain b", you selected the option that said it was a change of the domain.
Now, however you're trying to reuse "domain a" and you get that banner. however, this also tells me that whoever sees that banner is not a translation manager, but maybe just a translator? that's the part i'd like to know next.
--------------
You will keep having this issue as long as you migrate and you have anything from WPML in the database. however, may I have access to the site to try to see the banner because if you're a translation manager you should have an option to set that domain as a different site and not the one you moved thus removing the banner.
Hi Alejandro. First, I'm happy to give you access, but do not have the option to send a private reply. Please let me know how I can get you access and provide credentials.
This issue appears to be far more complicated than just that. Did you read through the previous ticket I'd submitted (https://wpml.org/forums/topic/migrated-site-and-now-seeing-an-error/)? If you have not, please do. It explains much of what happened before and hopefully provide more insight so your support can actually help.
In an effort to summarize things, I want to explain how we've done things up until this point and how we may be able to change the process based on your reply.
CURRENT PROCESS
We have two sites, XXX.com (production site with a production key) and staging.XXX.com (development site with a development key). Most times that we do any work on staging for testing purposes, they're minor enough to manually move over to production. However, what you see in the previous ticket was phase 1 of a redesign, which included a ton of new work. We use WP Migrate to PUSH staging to prod. Even though WPML is said to be compatible with WP Migrate (https://wpml.org/plugin/wp-migrate-db/), we continue to have this issue where the "Site Moved or Copied - Action Required" banner appears, along with the second banner that reads, "This site is registered on WPML.org as a development site. When this site goes live, remember to update the site key from "development" to "production" to remove this message." The bigger issue is that WPML wouldn't work on prod after this migration so we couldn't process any translations. The previous WPML supporter expressed that the issue was likely from an old version of the plugin, which is strange because we always keep the sites up to do. Either way, she helped us get both prod and staging up to date with the latest plugins, and the issue persists.
SUGGESTED PROCESS
We are about to enter into the second phase of this site's redesign and I need to ensure this won't happen again, particularly not being able to process translations. Would it be possible to do all of our work on staging as we always have, use WP Migrate to push to prod **with all WPML tables unchecked**, and attempt to sync the translations on prod once the migration is complete? This assumes that the translations we make on staging are saved elsewhere and can be synced to prod.
Ultimately, I'm open to your guidance, but this feels far more complicated than it needs to be and if a solution can't be found, my client may likely remove WPML altogether. Please let me know if more information is needed.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
You should be able to allow me access and once you do I'll be able to confirm the problem is what I think it is. it should be something that won't happen anymore from V4.9.3 onwards and that should be prevented already in the current 4.9.2 version (but if your issue started before that time which almost certainly it did, then you'll still need us for this last time).
The private reply field is for this next reply only and you need to tick a privacy checkbox first in order to see the fields.
Let's go ahead and wait so your time is well spent. If you would, please set the next reply with privacy settings and I'll send updated credentials for staging. Thank you, Alejandro! I'll be in touch soon!
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
I checked the site but it seems it's got a really low role for my user so I can't even access the backend. can you please allow me admin access, just so I check the things correctly.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Please check this video: hidden link
So far so good, I added the sitekey when requested by WPML and then added it to the WP-CONFIG file as well.
Right now I get the correct migration banner that asks you what you want to do with the staging site.
If you want to "destroy" the staging site, then you can select the other option that appears in the video, otherwise follow the instructions on the banner (found in WPML > Translation dashboard) and you should be ok.
After that's done, let me know if the problem returns (we may need to wait hours or a day for it to return if it actually does so) and I'll be able to talk to our devs and check everything else needed for this to not happen again.
Hi Alejandro. Thanks for the video, however I'm quite confused. I'm glad the site key issue has been fixed, but the issue I'm having wasn't knowing how to migrate the staging site to production (although your information will likely come in handy later); it's that I'm still seeing the message, "Site Moved or Copied - Action Required. Looks like this site is a copy of a different site, or moved to a different URL. Please contact your translation manager to update Translation Management plugin configuration." See the attached screenshot. There is no action I can take to remove it.
We will likely not be migrating the site for a few weeks, but I would like to keep this thread open until the time that we do in case I need to reach out again. Is it possible for me to reply even after a few weeks, or will the topic automatically close? I would hate to have to start this conversation over with someone new. Please let me know.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello there,
Maybe i was not clear enough. I didn't want to focus on the migration on its own, but I wanted to show you what happened on my end because i never saw that banner you showed me in your screenshot (As you can see in the video) and I actually still can't see it.
What I can see is the migration banner again. Now let me be more specific with my questions:
- did you see the banner you showed me in your screenshot right after you accessed your site? (not after going through the migration wizard myself)
- did you ever see the migration wizard i showed in the video?
- Did you push or made any change in the database from the 30th until today? because I'm seeing the migration wizard again but from the error logs I can see this started to happen today and there wasn't any wizard from apr 30th until today, which I'd like to confirm with you.
Hi Alejandro. It's very strange that you can't see the banner seen in my screenshot. I've seen it on staging ever since we pushed the redesign phase 1 updates via WP Migrate a few months ago.
To answer your questions (in CAPS):
- Did you see the banner you showed me in your screenshot right after you accessed your site? (not after going through the migration wizard myself) I ALWAYS SEE THAT BANNER WHEN I LOG IN. IT HASN'T APPEARED RANDOMLY OR DISAPPEARED. I USED TO SEE THE "DEVELOPMENT SITE" BANNER, BUT THAT CLEARED WITH YOUR RECENT WORK.
- Did you ever see the migration wizard I showed in the video? I SAW THAT ONCE BUT IT MAY HAVE BEEN ON OUR DEV SITE. (WE HAVE 3 SITES--PROD, STAGING AND DEV.)
- Did you push or made any change in the database from the 30th until today? Because I'm seeing the migration wizard again but from the error logs I can see this started to happen today and there wasn't any wizard from apr 30th until today, which I'd like to confirm with you. THE ONLY CHANGES THAT HAVE BEEN MADE ARE THE UPDATES OF A FEW PLUGINS. NOTHING ELSE.
Not to change the target, but would it be helpful for you to access our dev site as well? I'm seeing both messages on that site (see screenshot), not just the one banner.
Alternatively, should we just continue our work and connect with you when the time comes to migrate? I hate that this is so confusing 😛 Haha. Thank you!
I'm Olexander, a developer from the ATE/AMS team.
I've been looking into your case — yesterday I fixed
the issue on your staging site (staging.goldenstatelumber.com)
and everything should be working correctly there now.
Regarding your dev site, I believe I know what might
be causing the issue there as well. Could you please
share temporary WordPress admin access via a private
reply so I can investigate and fix it quickly?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Once we get the credentials for the dev site, we'll be able to fix that as well 🙂
As mentioned before, it's something that won't happen again once fixed because we're totally changing that workflow and making it streamlined (there won't be a banner anymore, at all).
