[Resolved] Accessing translation memory when sharing a WPML account
This thread is resolved. Here is a description of the problem and solution.
Problem: The client rebuilt their website using the Divi page builder and expected the translation memory and credits from the original site to be shared with the new site. However, after translating a page that was already fully translated on the live site, 200 credits were unexpectedly used. The translation memory did not seem to be shared as anticipated, possibly due to content segmentation issues caused by the Divi shortcodes. Solution: We reviewed the client's situation and confirmed that differences in content segmentation between the old and new site versions were causing the translation memory to not recognize the content as the same. We provided a detailed explanation through a video (video link). To address the issue of the unexpectedly used credits, we reassigned 20,000 credits to the client's account to compensate for the discrepancies and partial matches of the translation memory.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Symptoms:
After translating a page that was already fully translated on the live site, 200 credits were used instead of none, which was unexpected. The translation memory doesn't seem to be shared as anticipated.
Questions:
How can we access the translations already made?
Why isn't the translation memory being shared as expected?
I did actually include the example page that I re-translated in my original message to you, but your system stripped it out when it re-wrote my issue. Hey ho.
The page on the live set is: hidden link
The page on the dev site is: hidden link
You can only see the translation in the backend as it isn't live on either site, but both English-language versions are the same.
Thanks very much for your help in trying to resolve this issue.
PS In case it's relevant: the new version of this website is built with the page builder Divi, which inserts shortcodes into the content field when used. So it may be that this is disrupting the matching between old version and new version of a page. If this is the issue, is there a way we can match old page and new, or do we have to copy translated content across by hand?
It is actually relevant as the segmentation between the old and new content is difference, hence the translation memory isn't detecting the same content.
Here is a video explaining this in more details : hidden link
As mentioned in the original ticket we used 25,302 credits translating the site before we rebuilt it in Divi. I had assumed all of that translated content would be available when we migrated it to Divi since none of the content had changed. I understand why that isn't the case now, thanks for the video.
As we didn't have enough credits left assigned to the site to translate it again (40,000 credits were purchased by our client via us and assigned to the site for the purpose of translating it), we translated as much as possible using the 14,698 credits available.
Can you refund us the original 25,302 credits used? Or can you only credit us for credits used in the re-translation process? If so, we are currently at 11,948 but there will be more credits to reimburse.
