Problem: The client's API token key generated for linking to AST language services is not being accepted.
Solution: 1. We recommend checking for connection errors by navigating to WPML -> Support -> Advanced Translation Editor logs. 2. If no errors are found, the issue may lie with the token itself. In this case, contact AST support to verify if the token is correct and functional. 3. Should AST provide a new token, update it in the translation services settings within WPML and attempt to test the connection again.
Please note that this solution might not be applicable if it's outdated or not relevant to your specific case. If after trying the suggested steps the issue persists, we encourage you to open a new support ticket. We also highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us through the WPML support forum.
Problem: The client was unable to cancel translation jobs sent to MateCat through WPML. Solution: If you're experiencing issues with canceling translation jobs sent to a translation service like MateCat, we recommend the following steps: 1. Navigate to WPML > Translation Management. 2. Select the page you wish to cancel the job for. 3. Assign it to a translator and send it to translation from the basket. For detailed instructions, please refer to our documentation:
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket with us.
Problem: The client was unable to send a template string to their Translation Service (CrowdIn). The string appeared in the basket before sending but got lost during the process. This issue did not occur with a similar string in a different template.
Solution: We investigated and suggest the following steps: 1. Verify if the template "Front Landing TMPL" has been sent to Crowdin and check if it has been translated and delivered. 2. Check the WPML Jobs tab for the status of the translation jobs. If jobs were opened in a local translator and then canceled, they might not appear in WPML. 3. If you manipulated the database and emptied the icl_translate_jobs table, this could cause the issue. Instead, follow our recommended method to reduce the size of WPML tables: Reducing the size of WPML tables. 4. For the specific string that is not being sent, you can: A. Copy the translation from another language, as done with Bulgarian. B. Send the template to a local translator and use the Classic Translation Editor. C. Delete the problematic string in String Translation, update the template, and translate it again, possibly using translations from a similar string.
Please ensure to back up your site before making any changes.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your case, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please open a new support ticket in our support forum.
Problem: The client was unable to send content to a professional translation service because Northern Kurdish / Kurmanji, set as an LTR language with a Latin alphabet, is not natively supported in WPML.
Solution: We forwarded the issue to our translation service team to find a solution. After a few days, the team resolved the issue. We recommended the client to attempt sending the content for translation once more.
If you're experiencing a similar issue, we suggest trying to send your content for translation again. However, please note that this solution might be outdated or not applicable to your case. If the problem persists, we highly recommend checking the related 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 in the WPML support forum.
