we are using drupal 7.43, tmgmt 7.x-1.0-rc1 and gengo 7.x-1.0-beta4+1-dev

currently we activate gengo translator and it seems that all work fine, the job will be generated, I could see it in the online portal. After some time the job is translated - I checked this in the online portal, but the status from the job did not change from pending to translated.
Only if I push the button "Poll translations" the status get updated.

Is this the expected behavior? I expect that the status changed directly after the job was translated via a callback or something else.

Matroschker

Comments

Matroschker created an issue. See original summary.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented

Is your site reachable from the outside? Is the correct URL reported to gengo?

Matroschker’s picture

Matroschker CreditAttribution: Matroschker commented

Yes, the site is reachable from the outside. We use OHT translator too and there it works.
Where can I check this, in the Gengo Account API settings?
There I found a "Default Callback URL:", should I set this? Have you an example for this?

Bambell’s picture

Bambell CreditAttribution: Bambell at MD Systems GmbH commented
Category: Bug report » Support request

Hello @Matroschker,

Where can I check this, in the Gengo Account API settings?
There I found a "Default Callback URL:", should I set this?

Yes, absolutely. To receive callbacks from Gengo, the callback URL of your website has to be defined in Gengo's API settings page (on Gengo's website). The default callback URL for Drupal 8 is http://{your-website}/tmgmt_mygengo_callback. It seems to be the same for Drupal 7.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented

Setting the callback should not be necessary, we submit that information as part of the jobs we create.

Make sure the domain through which you access drupal is reachable from public, it woll only work then. Given that the value you set there is only the default, I don't think that setting it does anything.

Matroschker’s picture

Matroschker CreditAttribution: Matroschker commented

I've tried it onesmore with the callback url, for my site something like this https://{your-website}/tmgmt_mygengo_callback, but i got no automatically update of the jobs.

What I don't understand is why there is this button "poll translations" in every job? This should be done automatically, right?

We use OHT translator on the same site and there is no problem getting automatically update of a job, this runs since 2 or 3 years. But now we want to have a second translator. So I think there is no problem with the reachability.

If I change the callback URL, it is necessary to generate a new key?

miro_dietiker’s picture

miro_dietiker
Location Switzerland
CreditAttribution: miro_dietiker at MD Systems GmbH commented

As Berdir pointed out, the URL is submitted as part of the job. No setup is needed.
And keys also don't need to be regenerated.

So the problem seems to be somewhere else.
You could look at the apache log to see if you get some requests from Gengo that are somehow not processed to provide us more background.
Otherwise it's hard to help here.

Matroschker’s picture

Matroschker CreditAttribution: Matroschker commented

I checked my Apache logs (error and access). I can't find any errors related to Gengo. But I could find entries related to the OHT translator ([15/Jun/2016:02:44:39 +0200] "POST /en/tmgmt_oht_callback HTTP/1.1" 200 -) - so it seems the process works for OHT.

Once more back to #2 - In which form I should report an URL to Gengo? What URL is mentioned here? Is there another thing to do beside the callback URL, which I must not maintain?

miro_dietiker’s picture

miro_dietiker
Location Switzerland
CreditAttribution: miro_dietiker at MD Systems GmbH commented

"Onesmore..." => Once more, there is no manual URL to report/setup at gengo.

Anyway, are you sure that the URL you are when interacting with the system is the right public accessible URL? (not something like a xyz.local or so...)

We could retest the callback in 7.x once, but i fear we can not help without debugging your setup if a vanilla installation in simplytest.me or so just works.