Steps to reproduce:

1. Install Drupal (tested on 8.7.5) in English
2. Enable modules content_moderation, content_translation
3. Add a Language (e.g. German)
4. Enable translations of Article and Editorial Workflow
5. Create a new Article content and set it into published state in default language (English):
6. Add a German translation to the Article content, save it to Draft state
7. Go to /admin/content, see only the English version of the article appears in the List

Expected is that in point 7, admin content view shows English (Published) and German (Unpublished) versions of the article.

Note: If you keep both translations in Draft state, both items properly appear in the admin content view

Side Bug 1: The "moderated content" view properly displays the draft German article, however the "Content Type" column is empty.
Side Bug 2: If you edit the German translation of the Article and change moderation state from Draft to Published, it appears correctly in the admin content view. However, as you change the state of the Article from Published back to Draft, it appears in the admin content view with wrong "Published" state.

Issue fork drupal-3071916

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mirsoft created an issue. See original summary.

mirsoft’s picture

mirsoft commented
Title: Admin content view does not display unpublished translations of published nodes » Admin content view does not display unpublished translations of published nodes when content moderation is enabled
luca_loguercio’s picture

luca_loguercio commented

@mirsoft We're also experiencing the same bug. Were you able to resolve it? Thanks

Version: 8.7.5 » 8.7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.7.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and 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.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.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.

hmdnawaz’s picture

hmdnawaz commented

Any update on this issue. I am having the same issue.

scottcollier made their first commit to this issue’s fork.

kunalkursija’s picture

kunalkursija commented

I faced this issue too and indeed this seems to be associated with nodes following a "Content Workflow"(OR In other words, the content moderation module).

kunalkursija’s picture

kunalkursija commented

So I looked into this a bit and found out that the admin/content page is a view fetching data from the node_field_data database table. And after looking at the data in this table, I found below:

  • For multilingual nodes that don't follow content moderation workflows: There are only 2 states for the node/node-translations, Either published OR UnPublished. Now for both these states, Any edit you make to the node translation, A default revision is created. Which makes an entry to the "node_field_data" database table. And this is the table from which the '/admin/content' page fetches the data. So nothing misses out on the "admin/content" page.
  • For multilingual nodes that follow content moderation workflows: When we create/edit translations, A database entry for the translation is made to the "node_field_data" table. But, The entry happens only and only if the translation’s moderation state has the "default revision" flag enabled. For Ex: If you create a new "draft" translation of a published node, The entry won't be made to the 'node_field_data' table. Hence the translation draft won't be visible on the "admin/content" page.
berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Yes, this might be unfortunate, but I don't really see how this could be changed. To put #9 in different words, admin/content lists default revisions. Drafts, be that new translations or e.g. changing the title of a published translation are now showing up there.

kunalkursija’s picture

kunalkursija commented

True. For moderated nodes, The 'default revision' seems to be playing an important role and it makes sense to only keep 'published' & 'archived' states have default revision flag enabled(just what editorial workflow does).

I also tried to imagine creating the content page view from 'content revisions' and it's also not helping. As to fetch node data, Views creates 'joins' to 'node_field_data' table which only holds 'default revisions'.

mowens’s picture

mowens commented

Check out this thread. After this patch, newly saved translation drafts show on admin/content page.
https://www.drupal.org/project/drupal/issues/3088790

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
pere orga’s picture

pere orga
Primary language Catalan
commented
Version: 9.3.x-dev » 9.4.x-dev

@mowens I can reproduce this, thanks!

I may be missing something (very likely), but is there a reason why new translations should always not be the default revision? E.g. what's wrong in having a "draft" revision as a default revision if no published revision exists for that language? For the visitors, it would be an HTTP 403 in both cases

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Because only one revision can be the default revision *across all languages*. And yes, each revision and new revision always contains all translations.

pere orga’s picture

pere orga
Primary language Catalan
commented

Thanks again @Berdir, this is now starting to make more sense to me.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now 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.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now 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.

eduardo morales alberti’s picture

eduardo morales alberti
Primary language Spanish
Location Spain, 🇪🇺
commented

Is it a solution or a "workaround" to see the draft versions on the content view?

dullarobin’s picture

dullarobin commented

I'm also facing the same issue with Drupal 9.50. Steps to reproduce are given below

a. Create original content in Draft mode

b. Create the first translation in Published mode

c. Create a second translation in Draft mode

Only the first 2 pages appear on the content view page

Thanks

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

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.

Read more in the announcement.