Hello WPML Support Team,
I am facing an issue with WPML on our website and would appreciate your assistance.
We had installed the WPML plugin 7 months ago on our staging site:
roadtrd.stage.com
At that time, we used a significant number of automatic translation credits — approximately 100,000+ credits — to translate content into Arabic.
Recently, due to major updates on the website, we had to re-import/sync the site from production back to staging. After doing this, all previously translated Arabic content has disappeared, and it seems that the translation credits we used earlier are no longer recognized.
Now, WPML is asking for new credits to translate the same content again, even though we already consumed credits for these translations in the past.
This is causing a serious issue for us because:
• The Arabic translations are no longer available
• The previously used credits are not being reflected
• We do not have unlimited credits to redo the translations
We kindly request you to:
1. Restore our previously used translation credits
OR
2. Restore the Arabic translations that were already generated earlier
If needed, I can provide you with staging or admin access to investigate the issue further.
Please let me know what information you require from my side.
Looking forward to your support.
Best regards,
Abdul Rehman
This is kind of expected behavior. You need to make sure the sites are connected and sharing the same translation memory in order for them to share same translations from memory.
Please note that used credits cannot be restored. However, translation memory can be moved / copied.
Anyway, I checked your URL roadtrdcom.stage.site and can see three instances connected, all sharing the same translation memory with 2,571 segments. The original translations were created on the staging site around August 7 and used approximately 69k credits, so seems should be all fine and same as in original website.
If you are expecting something different, please let me know. Also, please check if the original translations were done on another URL, as currently they all share same memory as original staging site.
