Retranslate Pages without translation memory

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

Problem:
The client is updating a project and integrating an English version using WPML. They encountered issues with translation settings not being correctly configured, specifically with multiple translation engines active and a newly imported glossary. They are considering either deleting all English content in the test environment before moving to the live environment or resetting the translation memory for DE -> EN translations.

Solution:
We recommend deleting all English content/pages on the test environment and then transferring this version to the live environment. Since the domain changes, re-registering the page in the WPML backend will ensure that the old translation memory does not affect new translations. This approach is practical as it avoids potential migration issues related to translation settings.

If this solution does not apply to your situation, or if it seems outdated, 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 further assistance is needed, 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: Exception

This topic contains 1 reply, has 0 voices.

Last updated by bjoernK-5 3 days, 3 hours ago.

Assisted by: Waqas Bin Hasan.

Author	Posts
February 24, 2025 at 2:11 pm #16741473
bjoernK-5	Background of the issue: We have the following situation. We have taken over the project of a new client. This project was very outdated. We have therefore created a temporary environment for updating and testing purposes. We have updated the test environment and now want to integrate an English version. WPML was already installed and integrated before the update. No other language than German was used. As the old WPML account is to be closed. We are already using a new WPML account (this account) on the test environment. The data of the test environment will then be transferred to the live environment after completion (database / images etc.). The test environment will than probably be deleted. We have already automatically translated some things on a test basis. However, we noticed afterwards that some settings were not yet set correctly. For example, all translation engines were active, although only deepl should be used. In addition, a glossary has now been imported. Symptoms: We now have the same problem as described in this ticket - https://wpml.org/forums/topic/resetting-translation-memory-for-a-language/ “When I try to delete the existing translation and retranslate the page, it still uses the old settings from the translation memory.” Questions: We are now considering how to proceed. Perhaps you could tell us what would be the best way forward. We currently see two options. First, we could delete all English content / pages on the test environment. We would then transfer this version to the live environment. As the domain changes, we would re-register this page in the WPML backend. If we understand this correctly, the translation memory is URL bound and would not affect the new translations created, right? We would then re-translate the pages without the previous translation memory on the live environment. As a second option. We would ask you, similar to the linked ticket, to reset the translation memory for the DE -> EN translation. We would then re-translate the pages on the test environment and then transfer that version to the live environment. Then we would have to connect the test environment to the live site so that the new translation memory is also available on the live site. Or do you see another possibility? Many thanks in advance. Frederic
February 25, 2025 at 9:25 am #16744586
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Hi, Thank you for contacting the support. You can go for any of these options. IMO, the first one is more practical since you'd eventually change the URL and instead of running into migration issues later on, it's better to start with this. We can help in either case, please feel free to ask. Regards.
February 25, 2025 at 10:05 am #16744867
bjoernK-5	Thank you for the quick reply. We also assumed that the first option is the better one. Ticket can therefore be closed.