Paola Mendiburu
WPML Supporter since 11/2020
Languages:
English (English )
Spanish (Español )
Italian (Italiano )
Timezone:
Europe/Madrid (GMT+01:00)
|
Hi there,
Thank you for your message. I completely understand your concerns and I’ll clarify everything below in a clear way.
Regarding the glossary size, before the merge each website had its own glossary. When the two sites were merged, the glossary entries from both websites were combined. This means that one of the sites had around 600 additional glossary words, which were moved into the other site, resulting in a total of 800 words.
About the different ATE settings, the Advanced Translation Editor settings are site-specific. These settings are not migrated during merge, which is why you are seeing differences now.
Concerning the Translation Memory and the missing previous translations, unfortunately the translations created with Achterlicht and Knipperlicht are no longer available, and this does affect new translation jobs. The only way to restore the Translation Memory is to go to the previous translation jobs that still contain the correct translations, open them, and click on “Save Translation Memory”. This will repopulate the Translation Memory so it can be reused in future jobs.
You can safely add new translations. Existing translations will not be affected unless you explicitly retranslate or update them. However, since some Translation Memory entries are missing, new jobs may consume more credits than before because the system cannot reuse those past translations automatically. This explains the additional credit usage you are seeing.
|
daveB-3
|
Is the second tier check over? Just to be sure?
If so, I need to add:
- We migrated to a new environment, so merging the sites can't lead to more glossary items (there was just one glossary).
- The ATE settings (which engine to use, the context-text, settings, etc. should be manually set again on the new environment?)
- Going to 'previous translation job': you mean saving in adl.testontwikkeling.nl (the staging site)?
- We are also building another new site; when migrating this always happens, or?
Looking forward hearing,
|
Paola Mendiburu
WPML Supporter since 11/2020
Languages:
English (English )
Spanish (Español )
Italian (Italiano )
Timezone:
Europe/Madrid (GMT+01:00)
|
The problem originally was with how the migration was done.
So the next time you do a migration please use Duplicator or All in on wp migration. That way everything will work properly.
What you can do, as you as you don the migration contact us so we can check that everything is correct.
|
daveB-3
|
And regarding my other questions?
|
Paola Mendiburu
WPML Supporter since 11/2020
Languages:
English (English )
Spanish (Español )
Italian (Italiano )
Timezone:
Europe/Madrid (GMT+01:00)
|
Do you mean: Going to 'previous translation job': you mean saving in adl.testontwikkeling.nl (the staging site)? --> By “going to the previous translation job” we mean the translations that were created and saved on adl.testontwikkeling.nl, which is the staging site.
could you please tell me from which site you plan to run the migration?
|
daveB-3
|
No. These aren't answered:
- We migrated to a new environment, so merging the sites can't lead to more glossary items as you explain. We had 400 items, now it shows +-800 (but there are only 400?).
- The ATE settings (engine to use, the context-text, settings, etc.) should be manually set again on the new environment (so I have to manually fix it on alldayled.com?
|
Paola Mendiburu
WPML Supporter since 11/2020
Languages:
English (English )
Spanish (Español )
Italian (Italiano )
Timezone:
Europe/Madrid (GMT+01:00)
|
If you do the migration properly everything will work. Once you will do the migration please let us know so we can check if appears the migrated banner on the migrated site.
Everything should work properly.
|
