On 'Translate' tab on entity page e.g. node/% if there is no translation for the entity after changing a publishing status the tab still displays an old one status.
The bug disappears when entity have a translated version.
Moreover the module does not check that entity has no status field at all
Comment | File | Size | Author |
---|---|---|---|
#21 | Translate-8.9.x.png | 25 KB | quietone |
#21 | Content-8.9.x.png | 19.95 KB | quietone |
#20 | screen-2-on-content-page-correct-page-status.PNG | 26.06 KB | VarunKrSingh |
#20 | screen-1-on-translate-tab-for-one-node-wrong-status.png | 21.41 KB | VarunKrSingh |
#1 | taxonomy_content_translation.png | 66.6 KB | andypost |
Comments
Comment #1
andypostComment #2
andypostComment #3
andypostShould wait for #1987882: Convert content_translation routes to a new style controller
Comment #4
jhodgdonWe should probably postpone this until #1966436: Default *content* entity languages are not set for entities created with the API is taken care of, because I think it will prevent this problem.
Comment #5
andypostI'm not sure that issues above would solve.
Probably trouble in translation metadata, which is not updated
Comment #6
jhodgdonThe reason I suggested a connection is that it seems like when I've seen this issue, it goes away if the original node has the language set to a real language. Which #1966436: Default *content* entity languages are not set for entities created with the API will take care of.
Comment #7
andypostSure, but as you see the screenshot displays a taxonomy term translation that has no status but should have translation status
Comment #8
andypostChecked today the term translation again and found
1) edit translation links leads to entity edit but delete leads to translation delete
2) if language added after entity saved then add translation leads to
InvalidArgumentException: Invalid translation language (uk) specified. in Drupal\Core\Entity\ContentEntityBase->addTranslation() (line 746 of core/lib/Drupal/Core/Entity/ContentEntityBase.php).
Comment #9
andypostComment #10
andypostThe only thing that left here - no way to add unpublished translation
Comment #19
quietone CreditAttribution: quietone as a volunteer commented@vlkff, thanks for reporting this problem.
I test this on 8.8.x and was not able to reproduce the problem in the IS.
On a fresh install I added two languages and enabled content_translation. I then added an article and two translations. When unpublishing any of the translations only that translation was listed as unpublished on the content page. And deleting any of the translations did not alter the displayed published state.
And from #10
I test this as well as and successfully added an unpublished translation.
Therefore, closing this a cannot reproduce.
Comment #20
VarunKrSingh CreditAttribution: VarunKrSingh as a volunteer commented@quietone
This issue arise on translation page and not on content page. If you use more than two language than on translate tab the page status would be appear with wrong status.
Tested on Drupal 8.9.13
Comment #21
quietone CreditAttribution: quietone as a volunteer commented@VarunKrSingh, thank you for the clarification. When responding to an issue that is marked closed, which you think isn't fixed, change the status, in this case to 'Active', since there is no patch here. It is only by chance that I saw your reply.
I tested again, this time with standard install and Drupal 9.2.x, 8.9.x and 8.9.13. In all cases I was not able to reproduce the problem.
I tried to make it break, changing the status on either translation a couple of times. But always the status was correct on both the translate tab and the content page.
@VarunKrSingh, Can you provide complete steps to reproduce the issue (starting from "Install Drupal core").
Comment #22
quietone CreditAttribution: quietone as a volunteer commentedComment #23
VarunKrSingh CreditAttribution: VarunKrSingh as a volunteer commented@quietone, Thank you for looking into it. Apologies for not providing full information. The translate page showing correct page status when used individually but having the reported glitch when used with content moderation and workflow module.
The steps i followed as
1. Install Drupal via composer.
2. Enable Multilanguage for French and Spanish.
3. Create user group content author and content approver.
4. Enable Content moderation and workflow module with intermediate page status(draft, review,archive).
5. While creating node first time with draft status, it show status unpublished which is correct.
6. when i make status change draft to review, it show status unpublished which is correct.
7. when i make status change review to publish, it show status published which is correct.
8. when i make translation of node in french and spanish with published, it show status published of all which is correct.
all the above status are need to notice on translate page of a particular node. now we need to change the status of all translations and need to check status.
9. If i make parent node draft, french translation review and spanish translation published it shows published to all which is wrong.
10. If i make parent node publish, french translation draft and spanish translation archive it shows unpublished to all which is wrong.
thank you.
Comment #24
VarunKrSingh CreditAttribution: VarunKrSingh as a volunteer commented