Background of the issue:
I am trying to process a translation batch via Smartling, but the batch is automatically being authorized and completed without allowing our Localization Team to review, modify, and approve it. Smartling informed me that the issue might be due to an 'authorize': 'true' parameter in the API upload, which needs to be changed to 'false'. Here is the link to our Smartling API documentation on job authentication: hidden link.
Symptoms:
The job processed successfully, but due to the 'authorize': 'true' parameter, the workflow is bypassed, and the batch is automatically authorized.
Questions:
Is it possible to adjust the 'authorize' parameter in the WPML Translation Proxy?
Can this be changed in our own server settings?
Thank you for waiting. I was able to confirm the solution.
In this case, you need to go to WPML > Translated documents options and change it to "Save the translation post as draft". This way, you can review the translation before they get published. Check the image attached.
This will work for drafting posts once it's back into WordPress.
But our request was about the method used sending the translation request to Smartling. Not for receiving it from Smartling.
Smartling informed me that the issue might be due to an 'authorize': 'true' parameter in the API upload, which needs to be changed to 'false'. Here is the link to our Smartling API documentation on job authentication: hidden link.
This is Ahmed Mamdouh from the translation proxy team, and I'll help you with this ticket.
As far as I understand, you have a problem with the translation configuration, so please provide me with the website admin access to check the configuration and get back to you with a solution.
I will set your next reply as private so that you can safely share the credentials.
I deeply investigated the issue, and below is my conclusion:
When I checked the jobs tab, I found that you translated the old jobs using
"Smartling Language Services" and those jobs are completed, and some of them are still in-progress, as shown in the attached screenshot.
Right now, you have authenticated another translation service called "Smartling TMS", and this is a different service as shown in the translator tab, as shown in the attached screenshot.
So, this caused the following behavior:
1- All the old in-progress jobs will not be retrieved because it is not connected to the current translation service.
2- You can't send new jobs because the new translation service you authenticated doesn't support ISO code "en" for English language (and you can see this error in the logs you shared).
This can be avoided by doing a language mapping from our end and this will allow you to send jobs properly.
So, if you want to proceed with "Smartling TMS", let me know to add the needed mapping to allow you to send jobs.
Translations are back running. Not sure how Smartling TMS got in there.
Would you be able to modify the API call so Smartling isn't automatically authorized?
I am trying to process a translation batch via Smartling, but the batch is automatically being authorized and completed without allowing our Localization Team to review, modify, and approve it. Smartling informed me that the issue might be due to an 'authorize': 'true' parameter in the API upload, which needs to be changed to 'false'. Here is the link to our Smartling API documentation on job authentication: hidden link.
I checked the parameter you mentioned, and I’d like to clarify that the current integration was developed in a standardized way to serve multiple clients, not just a single setup, and changing this parameter will affect other clients. While I understand the challenge you're facing, any change to this integration requires careful consideration and development effort.
That said, I will escalate this issue to our development team for further review. However, please note that implementing a solution or workaround may take some time.
In the meantime, I recommend reaching out to Smartling support to see if they can offer any temporary workaround or advice from their side.
Kindly be informed that the problem has been resolved and the jobs have been passed successfully.
The problem happened because of the differentiation between the language codes in WPML and Smartling, so I added the needed mapping from "en" to "en-us" and from "es" to "es-la" and it solved the issue.
Please try to send some jobs again and let me know if you get any errors.
Best regards,
Ahmed Mamdouh.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
