freme-project / freme-project.github.io

Apache License 2.0
2 stars 0 forks source link

Translation tutorial does not work #297

Closed jnehring closed 8 years ago

jnehring commented 8 years ago

When I open the translation tutorial in google chrome / ms windows 8 and click the "try it out" button then the page scrolls to the top and no API call is executed. Maybe this is related to #292

ArneBinder commented 8 years ago

Maybe this is related to #292

no, I fixed the tutorial page, now it displays:

{
  "exception": "eu.freme.common.exception.ExternalServiceFailedException",
  "path": "/e-translation/tilde",
  "message": "External service failed: {\"Message\":\"System not available for requested language pair\"}",
  "error": "Not Found",
  "status": 404,
  "timestamp": 1474554585701
}
andish commented 8 years ago

MT Development environment has only EN-DE system available. Freme DEV is using it currently. In the middle of next week we will release MT and also FREME dev server will have then all FREME MT systems, including also EN-NL which is used in this tutorial.

ArneBinder commented 8 years ago

This works again. Can we close it?

jnehring commented 8 years ago

I just changed the Tilde API endpoint to live. So this issue is fixed.

borriellom commented 8 years ago

The tutorial is not working again and I'm getting the same error in Ocelot when sending a request to the e-Translation service. I always get the error whatever language pair I choose (I'm only using language pairs listed in the "Available Systems" section here.

I don't know if this issue should be reopened or if systems are just temporarily down.

Note that I'm using public systems (empty key parameter) and FREME "current" version.

jnehring commented 8 years ago

The issue is fixed on freme-dev. freme-live still uses the development version of Tildes MT API. So currently only the dev version of the tutorial works.

Thanks for the reminder. I will reopen the issue and close it when it is really fixed after next release.

Welcome back @borriellom :)

borriellom commented 8 years ago

Thanks :)

jnehring commented 8 years ago

Fixed through https://github.com/freme-project/FREMECommon/issues/38