Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Wrong Revision status in revisions list for a node in second language. I changed the state to publish but in the sc/node/{nid}/revisions
It is still showing (Draft/Edit).
Steps to reproduce: I am using Multilingual and content moderation modules.
1 Add another language for example (Simplified Chinese).
2.Create a Node in default language (example english)
3.Create a translation node sc/node{nid}/translations
4.Save the translation in draft.
5. Check in revisions tab (It will be draft)
6.Again save the translation and publish it.
7. Check the revisions list it is still showing (draft) instead of (published).
Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.
Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.
Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.
Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.
I've run into this problem as well and wanted to clarify the issue.
Clarified Explanation
When you have translated pages not set to the same state (e.g., published, draft, unpublished). The system will display the revisions based on the state of the original content. The translation node revision-log list will display the state of the initially created node, not the state of the translated node.
Revision Log Display: The revision log for the translated page will show the state of the original page, not the translated one.
Accessing Revisions: If the original page is published but the translated page is in draft, you won't be able to access the draft revision of the translated content from the view tab. Instead, the view tab will show the revisions of the original language content. This means that the translated page, which is supposed to be in draft, will display the published version of the original content.
Example Using French and English Content
Let's say you have an English page and its French translation.
Original English Page: Published
Translated French Page: Draft
Scenario
Revision Log: The revision log for the French page will show the state of the English page (Published).
Viewing Revisions: When you try to view the French page, you will see the published English content instead of the draft French content.
Since having content published unintentionally. Can we move this issue from normal to Major?
Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.
Comments
Comment #2
lomasr commentedSteps to reproduce: I am using Multilingual and content moderation modules.
1 Add another language for example (Simplified Chinese).
2.Create a Node in default language (example english)
3.Create a translation node sc/node{nid}/translations
4.Save the translation in draft.
5. Check in revisions tab (It will be draft)
6.Again save the translation and publish it.
7. Check the revisions list it is still showing (draft) instead of (published).
I checked with admin account.
Comment #7
rafaelrs commentedHey everyone,
Any update on this issue? We're facing a similar issue here with the revisions updating wrongly some translations.
Comment #11
delmarr commentedI've run into this problem as well and wanted to clarify the issue.
Clarified Explanation
When you have translated pages not set to the same state (e.g., published, draft, unpublished). The system will display the revisions based on the state of the original content. The translation node revision-log list will display the state of the initially created node, not the state of the translated node.
Example Using French and English Content
Let's say you have an English page and its French translation.
Scenario
Since having content published unintentionally. Can we move this issue from normal to Major?
Comment #12
acbramley commentedI'm unable to reproduce this issue following the steps from #2
Comment #13
acbramley commentedI actually think this has overlap or duplicates #2722307: Move translation based conditions into database query on revisions overview page
Can anyone confirm? Then we can close this issue.