I am trying to: Translate or do daily tasks on my website.
Link to a page where the issue can be seen: hidden link
I expected to see:
Not expect to see that green banner when I log in to admin panel.
Instead, I got:
The screenshot below...
This issue blocks my work on our staging site, which is expected to share translations with the production site.
On wp-config.php file there is no such line containing these: "1
2
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello!
Usually this issue happens when you select that you have moved the site to a new location, so maybe in teh past you had used the same URL as a staging site and then migrated the site to a production site.
It would be very important for us to know exactly what have you done so we can understand the scenario and try to see how we can improve our product, so can you write us the steps you tried when migrating the site initially from and to the staging site and also what were the next steps to made you get where you are right now?
that will help me understand what we can do next and how.
Hello,
Here is the use case:
1. Create a backup of tirport.com via All In One WP Migration plugin.
2. Copy the backup file to staging.tirport.com
3. Recover the original site on to staging.tirport.com
4. Start a new beta version of tirport.com on the staging area.
5. Add new content.
6. Translate new content.
7. Review the new version.
8. Backup the staging and copy it to production.
After recent update of WPML, if the current task contains something to be translated we cannot proceed.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
You mention:
Recover the original site on to staging.tirport.com
Do you mean you take a backup from the staging site (with all the new modifications) and then you migrate it back to the production site, right?
I'm asking because your step 4 then makes me believe that you might not run step 1 and 2 again from the staging site, so it's as if you deleted the content and recreated the domain.
If this is the case, then that might the reason why you're getting the message.
---------------
Here's how our migration logic works in this case:
- You have "prod" and "stg" sites
- You take a copy of "prod" and migrate it to "stg"
- You get a migration banner asking if you moved or copied the site and in here if you moved the site then you select one option and another if you copied it.
- You make all the changes in "stg" and then migrate the changes back to "prod"
- You get the same banner as before but in here it's very important what you will choose. if you choose that you moved the site ("no" option) then that means that the site where you select that option in, will now become the ONLY site that can use WPML and translations.
If you selected that option on the "prod" site, then "stg" will show a banner saying that the site moved to a new location".
If you delete stg, recreate it and migrate it from an old backup, you'll still get the same. if you just restore the domain or do anything that is NOT migrating the content again from "prod" to "stg" (using a migration dump from AFTER the migration) then you might get the same outcome.
I'd suggest that in the case you want to use and reuse the "stg" site without "strings attached" you select the "yes" option when the banner is presented ("this is only a copy").
-------------------
at this point i ask you:
- did you at any point selected that you had moved the site ("no" option)?.
- Did you ever delete the "stg" site or left it active?
- Did you migrate the site again from "prod" to "stg" using a more recent DB dump from prod?
Let me know so i can tell you what to do to fix the problem.
Frankly your (WPML) way of staging and comitting back to production is quite confusing.
Restating our steps:
1. Create a backup of tirport.com via All In One WP Migration plugin.
2. Copy the backup file to staging.tirport.com
3. Recover the original site on to staging.tirport.com
4. Start a new beta version of tirport.com on the staging area.
5. Add new content.
6. Translate new content.
7. Review the new version.
8. Create a new backup from the reviewed version on staging.
9. Copy that backup to production.
10. Commit staging backup to production.
We usually chose "copied" after the recovery on both sides. But I would appreciate if you point to a how-to document or kindly write what to choose during those migrations.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Let me know when you do what i suggest in the private answer, please, because i'll have to do a few things on my end to make everything appear as translated and work as it was before on your site.
Dear Alejandro,
Thank you for the diagnosis and further steps.
I will deal with it in a couple hours.
I will get back to you with the results.
For your information, same issue happening also with the second production domain in this account.
deportak.com
Will be in touch.
Dear Alejandro,
According to your directions, I have edited the database, flushed the cache and then took a backup.
Then I use this backup file to reconstruct the staging area.
I think it worked. Because it asked me the usual question. Screenshot below.
But unfortunately, since I have changed something in the database, (I think) pay-as-you-go payment information was reset. I have re entered the payment information.
We have done some automatic translations during this month. Which was about 15 or less than 20 USD due for 1st of September. But all are gone. Does that mean we also lost the translation memory? Because there was quite a collection there. And will the translation credit usage be reset? If so we will be in debt to you. How to solve this?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello!
The translation memory issue is normal, because what you are doing with my instructions is kind of resetting the info we have on your account. i have made a few changes on our end so you can see the translation memory on your site again (that's the entire reason of my last message: https://wpml.org/forums/topic/this-site-has-moved-to-a-new-location-7/#post-14198415 )
I made the changes on my end to "reconnect" the account to your old one and it should be working as expected now (i also cleared the current credits usage, so you now have a clean slate as well!)
You mentioned you had the same issue on another site, correct? in that site, did the problem appear after a migration from the same domain (from "site a" to "site a") or after a restore of the site, by any chance?
Hello and thank you.
Getting straight to the last question:
I think we did the same mistake there too. I still think that wpml workflow is confusing during backup / migration events.
So do we need to do the same actions there too?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
From what you've told me, actually, it doesn't seem like the problem was your workflow but something in the steps (that's why i've been asking so many details about it).
We can fix the problem in the same way here, but it would be really useful if you could tell me how you migrated the site back to itself, or if you actually did that, because the problem here doesn't happen when you migrate from SITE B to SITE A but when something like SITE A > SITE A migrations happen and i'm not sure how you can achieve that.
Because if that's the case, with that information we can prevent this from happening again (the entire procedure you had followed from staging to production and back was actually correct).
Second domain in order is deportak.com
Same routine has been conducted regarding the creating a backup and copying it to a staging domain.
We may have done a backup recovery from its own image recently, since we did some server upgrade / customizing tasks also. Not quite sure which WPML button was clicked there.
Uploading the current error message at the staging site.
Production seems to be in order by means of similar notices.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Alright, here the problem is slightly different.
In here it happened because you moved the site from staging to prod, however you left the staging site "active".
That's ok, but see it like this: this site has an older snapshot of the production site.
May i know what you'd like to do here on an "older" snapshot of the prod site? because in here, we would expect that you would import a DB dump or a migration from the prod site into the staging site and in there you'd end up getting the banner with the options, again.
Please let me know so i can understand what we can do here.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Alright, then if the message was encountered before any migration, then it's kind of expected (this is done to prevent you from using "translate everything" by mistake on 2 sites at the same time or well misuse your credits in 2 sites when you are only using 1).
At this point, you can migrate the site and you'll get the "correct" banner asking you what you want to do and from what i've seen you've been doing that correctly the whole time 🙂
