Problem/Motivation

If I go to the Lingotek module settings, I can set that all content translations download in the same status as the source, always published or always unpublished.

If I set that as “always unpublished”, and download a node translation, the translation is downloaded as unpublished as expected.

However, If I set that as “always unpublished”, and download a taxonomy term translation, the translation is downloaded as published, which was not expected.

Steps to reproduce

  • Enable taxonomy term translation for a vocabulary in Drupal content translation settings.
    • Ensure the “status” is marked as translatable.
  • Enable taxonomy term translation for that vocabulary in Lingotek content translation settings.
  • In Lingotek settings, set that all content translations should be downloaded “always unpublished”.
  • Roundtrip a taxonomy term for that vocabulary. It should be downloaded as “unpublished”.

Proposed resolution

If I set that content should be downloaded as “always unpublished”, a taxonomy term translation needs to respect that setting.

Remaining tasks

Patch with tests.

User interface changes

None.

API changes

None.

Data model changes

None.

Comments

penyaskito created an issue. See original summary.

penyaskito’s picture

Issue summary: View changes
penyaskito’s picture

Issue summary: View changes
penyaskito’s picture

Status: Active » Needs review
StatusFileSize
new8.84 KB
new10.53 KB

Added patch with tests. This would also fix other entities aside of taxonomy terms, e.g. Drupal commerce products.

hlopez credited sowmiya_v.

hlopez’s picture

Status: Needs review » Reviewed & tested by the community

Patch tested by me and reviewed by @sowmiya_v, looks good! Thanks!

  • penyaskito committed afae2fd on 3.8.x
    Issue #3247828 by penyaskito, sowmiya_v, hlopez: Translating a taxonomy...

  • penyaskito committed be36c2a on 4.0.x
    Issue #3247828 by penyaskito, sowmiya_v, hlopez: Translating a taxonomy...
penyaskito’s picture

Status: Reviewed & tested by the community » Fixed

Committed afae2fd and pushed to 3.8.x.
Cherry-picked be36c2a and pushed to 4.0.x. Thanks!

Status: Fixed » Closed (fixed)

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