Falls diese Lösungen Ihr Problem nicht beheben oder falls sie veraltet erscheinen, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Bitte überprüfen Sie auch die bekannten Probleme, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: The client noticed a discrepancy in the number of credits used for automatic translation from Hebrew to English, with the system using 64,216 credits which seemed too high compared to the actual word count. Solution: If you're experiencing a similar issue, it's important to understand that each word may consume a different number of credits depending on the Automatic Translation Engine used. For the PTC engine, each word uses 4 credits. For detailed information on translation pricing, please visit Automatic Translation Pricing. To view an invoice of the credits used, you can follow the steps outlined here: Automatic Translation Invoices.
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.
Problem: The client is unable to transfer credits from one site to another due to an incomplete migration, resulting in an error message when attempting to withdraw credits to their WPML account. Solution: We identified that the migration for the websites was not completed correctly. If you run into a similar issue, we recommend opening a new support ticket and ask for our assistance.
Problem: The client needed to roll back translations on their Divi template because unwanted sections were translated. They only wanted to translate pages and blog posts. Solution: We explained that once credits are used for translation, they cannot be restored as WPML compensates the translation engine immediately. We asked the client to specify the amount of credits they were expecting to return for Divi library layouts.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly recommend checking related 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.
Problem: The client reported that the automatic translation was not working on their production website due to a credit allocation issue. The backend displayed a message stating insufficient credits, despite having over 42,000 credits. Additionally, an old development URL was incorrectly listed in the credit management and could not be removed. Solution: We resolved the issue by updating the credit allocation settings on our side. We ensured that the website/key mapping was corrected and that the domains were no longer grouped incorrectly in the WPML credits view. We advised the client to refresh their WPML.org account page to confirm that the changes were reflected correctly.
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 https://wpml.org/forums/.
