Background of the issue:
I am translating on both production and staging sites. According to the documentation, items that are already translated should not be charged again.
Symptoms:
Credits and translations are not shared between production and staging, resulting in double costs.
Questions:
Why are translations being charged again on the staging site?
How can I ensure that translations and credits are shared between production and staging?
would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to a testing site where the issue is replicated.
You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this:
The Translation Memory is valid only for texts that are the exact same. There can't be any differences between a segment and the segment that will use its Translation Memory. Even a blank space or a dot is enough so that WPML understands that the segments are different and thus shouldn't have the same translation. I just wanted to bring this, as I think it might be helpful.
As for the issue, can you please test something for me? I want to verify if we can reproduce this behavior. Please make a full website backup before proceeding.
1. In the staging version, make a small change to a text of a given Occupations post. You can add a word or a blank space to it;
2. Translate that segment to a secondary language and save;
3.In the production version, copy the segment you altered in the staging and replace the original text with it. It's important that this segment is identical to the staging's one;
4. Click on the plus/edit sign of the secondary language you choose on step 2, in the pages tab.
5. Inside the translation editor, click to add a translation to the segment. Check if the translation is pulled from memory;
It would be great if you could share a screen recording of your testing. I can recommend you Loom to record your screen, it's free: hidden link
As I said, this will give me information on how the feature is working on your website.
A quick question: what is the name of the exact CPT you mentioned you noticed the issue on?
Oké thank you. I will test this tomorrow morning with a fresh head so I don't make mistakes. I just fixed a whole issue with unintentional translations in my listing grid on my production site. It was showing all languages mixed while they where hidden.
Sorry but it did not happen for one occurance. As the screenshots show I lost about 2x 30K credits between translation on staging and production. I translated through the translation management system and translated to Dutch and German for:
CPT type measure
CPT type occupations
Pages
Templates
Listing components
In total I made 649 translations. These are all the translations marked as 'waiting for review' under the translation management tab in the backend.
We analyzed what went on. The Translation Memory was not updated in time, that's why you got double charged. Since this is on us, I've refunded you 80k credits. Please confirm if you received them.
As a recommendation to avoid that in the future, you can translate your content directly in the production website and set them to be reviewed before being published, in WPML > Settings. If you translate content in the staging website, please wait at least 5 minutes, before sending the same content to translation in the production version.
