'Error Could not retrieve translation' on Dutch page


(Jan Willem) #1

There’s something wrong in the Dutch-section. I get a “Error Could not retrieve translation” message while entering “Help out on a translation”. Hopefully it’ll be resolved soon because we’re near 100% there :slight_smile:


(Jan Willem) #2

Wordt (als het goed is) vandaag opgelost is mij verteld.


(Mike) #3

Still having issues? Looks ok to me now, but let me know if you’re seeing otherwise


(Jan Willem) #4

Still issues. No new page after “Please enter a translation in Nederlands” -> Pressing “Save and go to next translation”…

Jan Willem.


#5

Tja is niet goed joh!


(Jan Willem) #6

Helaas is de storing nog niet opgelost maar via een omweggetje zijn alle nog openstaande vertalingen voor 100% verwerkt! Finetuning is hier en daar nog wel nodig…

Bepaalde uitdrukkingen zijn wat lastig naar het Nederlands te vertalen, andere moeten naar mijn idee gewoon in de Engelse taal blijven.

Wie heeft een goede suggestie voor vertaling van ‘Pick’.


(Danny Dulai) #7

Hrm… I see errors in the logs on the server-side from before… but I cant reproduce the error.

Are you still having the issue? Anything you can tell me would help…


(Jan Willem) #8

Here are the steps I follow to get to the error:

  1. Entering the Welcome screen
  2. Chosing ‘Nederlands (Dutch)’
  3. Chosing ‘Help out on an translation’
  4. The following Error appears:

Error
Could not retrieve translation.
OK
{
“line”: 5615,
“column”: 28,
“sourceURL”: “https://translations.roonlabs.net/build.js”,
“original”: null,
“response”: {
“req”: {
“method”: “GET”,
“url”: “/orm/strings-random/dutch/app”,
“headers”: {}
},
“xhr”: {},
“text”: “{“reason”:“NoTranslations”}”,
“statusText”: “Internal Server Error”,
“statusCode”: 500,
“status”: 500,
“statusType”: 5,
“info”: false,
“ok”: false,
“redirect”: false,
“clientError”: false,
“serverError”: true,
“error”: {
“line”: 5556,
“column”: 22,
“sourceURL”: “https://translations.roonlabs.net/build.js”,
“status”: 500,
“method”: “GET”,
“url”: “/orm/strings-random/dutch/app”
},
“accepted”: false,
“noContent”: false,
“badRequest”: false,
“unauthorized”: false,
“notAcceptable”: false,
“forbidden”: false,
“notFound”: false,
“headers”: {
“access-control-allow-origin”: “",
“cache-control”: “private, no-cache, no-store, must-revalidate”,
“connection”: “keep-alive”,
“content-length”: “27”,
“content-type”: “application/json; charset=utf-8”,
“date”: “Tue, 28 Nov 2017 15:29:12 GMT”,
“etag”: “W/“1b-/8VkAz/bUeHPx+Bkfx7v41BOmbc””,
“expires”: “-1”,
“pragma”: “no-cache”,
“server”: “nginx”
},
“header”: {
“access-control-allow-origin”: "
”,
“cache-control”: “private, no-cache, no-store, must-revalidate”,
“connection”: “keep-alive”,
“content-length”: “27”,
“content-type”: “application/json; charset=utf-8”,
“date”: “Tue, 28 Nov 2017 15:29:12 GMT”,
“etag”: “W/“1b-/8VkAz/bUeHPx+Bkfx7v41BOmbc””,
“expires”: “-1”,
“pragma”: “no-cache”,
“server”: “nginx”
},
“type”: “application/json”,
“charset”: “utf-8”,
“links”: {},
“body”: {
“reason”: “NoTranslations”
}
},
“status”: 500
}


(Danny Dulai) #9

ok found the issue… YOU ARE DONE.

Wow! This is not a case I would have expected. You have translated or voted for EVERYTHING in Dutch. So there is nothing for you to help out on.

Maybe try another language? :wink:


(Jan Willem) #10

Haha. Ok, I’ll start with Chinese tomorrow :blush:
But the best thing to do is asking anyone else involved with the Dutch translation if they can work there without these errors.
Anyone?