Error with copying translation information to new URL

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

Problem:
The client was trying to create a staging site using WP Staging and encountered an error after selecting that the staging site is a copy of the production site. The error message was 'Error with copying translation information to new URL'. Additionally, the client faced issues with deactivating the registration, which kept spinning, and the site remained 'registered' with the production site info. The client also noticed that the REST API was disabled on the staging site, which differed from the original site.

Solution:
We recommended following the instructions from our documentation on Using Advanced Translation Editor when you move or use a copy of your site. If the button to enable the Advanced Translation Editor on the staging site was not present, it indicated that the problem might be different, and we would need access to the site to investigate further.

Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket 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: Bug

This topic contains 4 replies, has 2 voices.

Last updated by Alejandro 10 months, 3 weeks ago.

Assisted by: Alejandro.

Author	Posts
February 7, 2024 at 7:44 pm #15278841
jackH-4	I am trying to: Create a staging site using WP Staging. Link to a page where the issue can be seen: Internal I expected to see: A working staging site Instead, I got: After I copied using WP Staging and signed into the Stage site. WPML asked me about if this is a copy of the production site. I selected Yes. But got this error message: Error with copying translation information to new URL I have also tried to deactivate the registration. It doesn't work. It just kept on spinning and the site is still "registered" with the production site info.
February 8, 2024 at 10:24 am #15280435
Alejandro Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	Hello! This is an interesting case and i wonder ifyou can follow the instructions from here: https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/using-advanced-translation-editor-when-you-move-or-use-a-copy-of-your-site/#using-wpml-on-two-domains if the button is not there, then it means that your problem is different and in that case i'd ask you to please allow us access to your site so we can further investigate what's going on.
February 9, 2024 at 12:50 pm #15286160
Alejandro Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	Can you watch this video? --> hidden link I do not see the problem happening. i selected the copy option and then everything worked normally. Can you tell me if you did something differently?
February 9, 2024 at 5:09 pm #15287148
jackH-4	You must have magic hands! Thanks. The only thing I changed is the WP memory. It only had 40MB and I noticed it in the support section. So I changed it to 128MB. Can you look at this issue? https://wpml.org/forums/topic/traditional-chinese-subtotal-in-woocommerce-overwritten-by-wpml/#post-15278844 The reason I created this staging is to fix that issue. But the support is taking a very long time. Each response will take a day. Can you look into that? Thank you.
February 12, 2024 at 11:39 am #15292795
Alejandro Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00)	I took the ticket and i'll check the staging site to see if i can see the problem there as well. I can see this issue seems to be solved but i will leave it open for another 7 days in case this problem returns. The issue of the strings will be handled in the other ticket, instead. Regards.