<b>Background of the issue: </b>
I previously reported an error on this. That time I was unsure the error was human or WPML. This time I documented every step. To be safe - I paused my automatic translations before this change so no content is altered, however I am stuck now.
I am trying to import a glossary update via WPML. After importing an update for one language only, I found that other translations in other languages (Dutch, English, German, Spanish) were incorrectly altered. We confirmed that these errors were not present in our prepared file (glossary_items_updated.csv). They appeared only after importing into WPML. We confirmed this by directly exporting the glossy again after the import and making a comparison.
<b>Symptoms and observations: </b>
- Previously we imported a very big glossary into an empty glossary and that seemed to work.
- This import file was based on that current glossary, with 131 updated and 36 newly added Portuguese terms.
- These errors were not present in our prepared file (glossary_items_updated.csv) but appeared after importing into WPML.
- Included the files we used hidden link
- I can provide a staging environment to test these errors.
<b>Questions: </b>
- Why are translations in other languages being altered after importing the glossary update?
- How can I fix the glossary based on glossary_items_updated-7-May.csv
- How can we prevent this in the future updates
