Problem/Motivation

Steps to reproduce:
First, I upload content (in this case I just use a basic article) and go through the whole translation process and then download the translations back to my drupal site. Then I go back into TMS and add a review phase to a few targets (I ususally do Chinese, Japanese, and Korean) and I add a new to rule to the Machine Translation to phase to call the project callback URL when the MT phase is marked complete. Next, I return to D8 and edit the article. I upload it to TMS and wait a bit for the content to go through the workflow. Then, after TMS says all the MT is done, I return to Drupal and execute the Check Progress of all Translations. And that is where I am getting inaccurate statuses.
If I execute the Download All Translations actions I get the correct dark blue for complete translations and turquoise for interim translations.
I've attached a screenshot below of what I am seeing in Drupal. Notice how after the Check Progress has been executed all but JA and ZH are turned green showing ready for download, even though KO was another target with the extra step added to it.

Proposed resolution

They should be shown as "Ready to download", even if there are uncompleted phases.

Remaining tasks

Fix + tests.

User interface changes

Even if phases are not completed, they should be shown as "Ready to download".

API changes

None

Data model changes

None

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

penyaskito created an issue. See original summary.

penyaskito’s picture

The last submitted patch, 2: 2733613-2.only-tests.patch, failed testing.

The last submitted patch, 2: 2733613-2.only-tests.patch, failed testing.

The last submitted patch, 2: 2733613-2.only-tests.patch, failed testing.

penyaskito’s picture

Status: Needs review » Reviewed & tested by the community

Tests passed and failed as expected.

  • penyaskito committed be6d7c1 on 8.x-1.x
    Issue #2733613 by penyaskito: Some target statuses are not getting...
penyaskito’s picture

Status: Reviewed & tested by the community » Fixed

Committed and pushed to 8.x-1.x!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.