Background of the issue:
I'm working on our WPML setup in a multidev environment. We have a unique environment where developers work locally and merge with the main Dev trunk. Code moves from Dev to Staging and then to Live. Content changes only happen in Live, and content from lower levels never get pushed up to Live. I want to build and test my localized site in multidev, validate the output, then move that translation memory up to live. I do not want to pay for translations twice.
Symptoms:
I need to preserve the translation memory database across environments.
Questions:
How do I preserve translation memory database across environments?
What is the best way to move translation memory from multidev to live?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
It depends if any of the sites have a subscription for automatic translation credits.
If both sites have active, separate accounts for automatic translation you need to:
- Cancel the account on one of these two sites.
- Wait for the charge to be triggered for the canceled account (usually takes about an hour).
- Pay the final invoice for the canceled account.
- Get the migration code from the site with the canceled account and enter it into the site with the still active account.
The topic ‘[Closed] How do I preserve translation memory database across environments?’ is closed to new replies.