Problem: You need to convert Custom Post Type (CPT) A to CPT B on your site and want to ensure that all posts under CPT A and their translations are preserved during the conversion. Solution: The functionality you are asking about is not related to the translation of your content, which means that it falls outside of the scope of the WPML plugins. If you need a custom solution, we recommend contacting one of our certified partners. They will be more than happy to help you with this. You can find a suitable partner at https://wpml.org/contractors/.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. 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. If this does not resolve your issue, please open a new support ticket at our support forum.
Problem: The client is using a hybrid approach for translations on their website, with some pages manually translated using WPML and others using Google Translate via the WPML plugin. They are unsure how they will be charged for translations via Google Translate, both for initial translations and subsequent edits. Solution: We charge only once for the translation of a page. WPML remembers the translations that have been done. If there are updates to the page and it is re-sent for translation, WPML will only charge credits for the new or edited content, not for parts that have already been translated. We utilize a translation memory to keep track of translations and ensure efficient credit usage. For more information on how WPML keeps track of your translations, please visit our documentation on translation memory.
If this solution doesn't look relevant to your situation, please feel free to open a new support ticket in our support forum.
