Getting error while translation using smartling service

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.

Tagged: Translation Service

This topic contains 6 replies, has 2 voices.

Last updated by Dražen 1 year, 3 months ago.

Assisted by: Dražen.

Author	Posts
September 14, 2023 at 5:46 am #14393353
seemaD	When I try to translate any articles I am getting the following errors. please help us to solve this issue. 09/14/2023 05:36:32 am - call - hidden link - {"api_version":1.1,"project_id":17067,"batch":{"source_language":"en","target_languages":["fr","it"],"name":"StockX News\|WPML\|en\|17","deadline":1694822400},"accesskey":"UNDISCLOSED"} 09/14/2023 05:36:32 am - response - {"status":{"code":29,"message":"This service does not support translation from en","debug":""},"response":null} 09/14/2023 05:36:32 am - error - (29) This service does not support translation from en
September 15, 2023 at 7:27 am #14400941
seemaD	WPML provides English (en), but our default language is English (en-us), and the URL looks like hidden link. Now our requirement is to configure English from "/en" to "/en-us", but our URL should look like hidden link. instead of hidden link. Similarly, we have to configure other languages in the WPML like "/it" to "/it-it", "/fr" to "/fr-fr", etc., and the URL should look like hidden link, etc. So we request that you please help us configure these requirements to fulfill our goals. Thank you.
September 18, 2023 at 5:59 am #14409109
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+01:00)	Hello, I am afraid the only way of changing en to en-us is by creating a new custom language with that language code. In that way, you would also need to duplicate all your pages from old language to the new one. - https://wpml.org/documentation/getting-started-guide/language-setup/editing-wpmls-languages-table/ - https://wpml.org/faq/how-can-i-assign-or-change-language-code-to-existing-content/ I am afraid there is no other easy way to do so. Also, your URL will then look like for example hidden link. Is this change really necessary? Since it would be better to continue to use original standardized language codes. Regards, Drazen
September 18, 2023 at 7:02 am #14409361
seemaD	Hi, We also tried to add custom language for en-us. but while creation we are getting error "Default locale already exists".
September 18, 2023 at 8:53 am #14410221
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+01:00)	Hello, probably that is the locale already used for your default English language. You can use a different one if you wish, it not important for language code. Locale is what is used to download already-made translation files from WordPress, and I think en_US, is used for default English. In your case, you want to make sure the language code is en-us, or whatever you wish to use. Regards, Drazen
September 18, 2023 at 10:53 am #14411245
seemaD	Currently getting this error. 09/18/2023 10:51:43 am - call - hidden link - {"api_version":1.1,"project_id":17084,"batch":{"source_language":"en-us","target_languages":["fr-fr"],"name":"StockX News\|WPML\|en-us\|5","deadline":1695168000},"accesskey":"UNDISCLOSED"} 09/18/2023 10:51:43 am - response - { "status": { "code": 0, "message": "success!", "debug": "" }, "response": {"batch":{"id":83352}} } New threads created by Dražen and linked to this one are listed below: https://wpml.org/forums/topic/split-getting-error-while-translation-using-smartling-service/
September 18, 2023 at 12:38 pm #14411909
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+01:00)	Hello, We limit 1 issue per 1 ticket, to keep things clear and easy to follow. I have opened a new ticket for your new issue: - https://wpml.org/forums/topic/split-getting-error-while-translation-using-smartling-service/ If the original issue of this ticket is resolved (custom language) I advise closing this one and continuing our conversation in the new ticket. Regards, Drazen