Home›Support›English Support›[Resolved] Existing pages are already translated but trying to charge full transaction
[Resolved] Existing pages are already translated but trying to charge full transaction
This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is experiencing an issue where changes made to an English page, specifically adding a new h1 tag and an icon, are not being reflected in the translated versions without incurring additional full translation charges.
Solution:
We identified that the main issue stems from the site not being connected to the Translation Memory before making these changes. To resolve this, we recommend connecting your sites to the Translation Memory to ensure translation consistency and avoid similar issues in the future. For detailed instructions on how to connect your sites, please refer to our guide on Automatic Translation Subscription for Multiple Sites.
Additionally, it's important to ensure that during migrations or site copies, the sites are correctly connected to the Translation Memory. This step is crucial for maintaining translation consistency across different environments.
As a one-time gesture, we have deposited 300,000 credits into your account to assist with the translations.
If this solution does not apply to your case, or if it seems outdated, we 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. Should you need further assistance, please do not hesitate to open a new support ticket 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.
1) Did you make any changes to the original language version of this post — hidden link — before updating its Chinese translation?
No changes made, you can also see many examples of this issue, in screen shot after I added the connecting code. Showing that the status of translations on live site did NOT change after connecting the 2 sites....
Sorry for the delay. Our developers are still working on this bug. We will get back to you as early as possible. Please wait. Thank you for your kind understanding and patience.
Please try and understand from my perspective we have been able to move site to fresh WP install and it is now really fast and we are now working on improving the user interface.... example
Now
hidden link
Before
hidden link
And we would be able to roll out these USI improvements on the translated pages... BUT This bug means we will be charged again .
So can you give me an indication of when it will be fixed and I again ask why not just apply credits and let me continue as normal ?
Lastly can we do anything to help your dev team example a copy of the live and dev sites ?
Please do answer my question directly on why not not go the free credits route,,,, if we get over this hurdle I have many more translation to run and you will be quickly paid back...
Thank you for the updates. As we mentioned earlier, this is a specific case caused by the export and import of posts to the live site. As a result, the translation memory is missing, which leads to extra charges when translating or updating a post.
We hope you are getting the expected results when translating or updating translations on your staging site: hidden link
For example, for posts like this one: hidden link
We have a request for tracking this: please create a new test post on your live site (hidden link) with similar content to the following posts, and translate it to one of the secondary languages (for example, Spanish) using the WPML Translation Editor. Then, check whether the translation memory is working as expected.
hidden link
hidden link
If it is not working, please share the URL of the test post so we can investigate further. Thank you for your kind understanding.
Also, please note that we have now deposited 100,000 translation credits into your account.
Thanks but can u clarify is it now fixed and you wish me to test on the live site.
As I do not understand purpose of below... request
I am not translating on staging, my site has gone live weeks back,.
We hope you are getting the expected results when translating or updating translations on your staging site: hidden link
For example, for posts like this one: hidden link
We have a request for tracking this: please create a new test post on your live site (hidden link) with similar content to the following posts, and translate it to one of the secondary languages (for example, Spanish) using the WPML Translation Editor. Then, check whether the translation memory is working as expected.
hidden link
hidden link
If it is not working, please share the URL of the test post so we can investigate further. Thank you for your kind understanding.
We now expect that translation will work as expected for posts on the development site as well as for new posts on the live site. This is because the existing posts on the live site were created and translated using the export and import method, and they do not have any translation records on the ATE server.
Therefore, it would be great if you could follow the steps we previously requested to confirm this:
Thank you for the updates. As we explained earlier, the import process correctly links the original posts with their translations. However, the translations in the Advanced Translation Editor do not pull content from the Translation Memory, because the site, post, and translation job IDs differ from those on the live site. This is why additional charges are being applied.
Just to confirm, are you planning to follow the same steps for migrating the other website, as mentioned in your earlier message: “Also, I wish to follow the same process with another website. Will I encounter the same issues?”
Please confirm whether you intend to proceed with the following steps:
1) Creating a staging site (hidden link) for the live site (hidden link)
2) Deleting the existing live site (hidden link) and setting up a new WordPress installation at the same domain
3) Exporting the posts (original and translations) from the staging site (hidden link)
4) Importing the posts (original and translations) into the new live site (hidden link)
Let us know if that is correct or if you plan to take a different approach.
He also asked what is the correct way to achieve the same outcome..
ALSO Developer Asking on how we can fix the issue and avoid all these extra charges
The question is...After importing the post and getting the new IDs, what needs to be updated in the rvrentacampervan database to link those translations?
Our understanding is as follows
When we translate Post A to French an ID of the translated post is held on WPML database and the same ID is held on the rvrentacampervan database( linking the post and translation )
When we do the import we lose that ID which is replaced with a new ID.
So can we amend the ID on our database to match the original ID solving the linking issues
Thank you for the confirmation. Replacing the post ID of the original language post and its translations after importing them into the new site is quite difficult. This is because the post ID is a unique value and would need to be updated in multiple database tables. Attempting this could lead to fatal errors.
Therefore, we recommend trying the following steps after taking a full site backup (this is mandatory). We hope this will help resolve the issue on the new site where you're importing the posts.
Create a staging site (hidden link) from the live site (hidden link).
In the ATE migration wizard, confirm it as a new Site URL, not as a copy of the live site. Refer to the following doc for more details:
Site A the first site
We have put too much work and time into changes on the live site to go back to the old version....
The main chnages are not actual contnet but improving the UI example see
old and new versions hidden link hidden link
So as you can see improvemenst are layout, but as you can undersatand when I run the translator to improve the UI of the translated pages,,, your system charges mew again
You did give some credits, thank you , but they are being used up quickly and will not cover the extra costs for duplicate translations over the migration time period.
To close this ticket I think it would be only fair to check my billing over this period and offer the same amount in free credits.
I will take the hit cover any additional costs for future duplicate translation, but you should at least cover existing costs...
