Background of the issue:
I am trying to clear the message 'This is only a copy - original site is still running' from my WordPress admin page. The issue can be seen at the following URL: hidden link.
Symptoms:
I expected the message to be cleared out, but instead, I got an error: 'Error with copying translation information to new URL. WPML was unable to copy your site's translations, translation memory, and glossary to this new URL.'
Questions:
How can I clear the message 'This is only a copy - original site is still running'?
What causes the error with copying translation information to a new URL?
If the issue continues, I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.
Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.
Your upcoming reply will be treated with confidentiality and will only be visible to you and me.
✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.
Thanks for your reply. I've corrected the configuration for you and that error message should be gone now.
However, I'm seeing this new error. Could you please make the folder writable on your server? You can reach out to your hosting provider if you're not sure what to do here.
WPML String Translation is attempting to write .mo files with translations to folder:
/files/languages . This folder appears to be not writable
Thank you for your help! We see the issue is resolved on that test environment. Can you please provide us details on what you changed so that we can make the same change on our primary dev server? That is where the issue first started, and this environment you corrected is one we stood up to give you access to - now we need to replicate the fix on our main dev server.
