Hi there,
If custom parameters for content is activated in admin/config/regional/content-language, when i am saving content, the content entry in admin/content is duplicated .
It has nothing to do with version because both entries are in the same language and with identical content, the node id is the same.
When i delete one entry it deletes both
Only one language is set in admin/config/regional/language
( i have deleted english after creating french )
Configuration Translation, Interface Translation and Language are activated.
ps: i am using revisions and content moderation with published workflow state being default revision
i am using admin views to display admin content
dunno if these 2 specificities might have an effect
best,
Mathieu
Comments
Comment #1
matoeil commentedmatoeil created an issue.
Analyzing this further it turns out to be an artefact
This happened because i have modified the admin/content view , adding the relations Content moderation ,and revision User , in order to be able to display the content moderation state and the user that did the revision
the admin/content SQL is
SELECT node_field_data.langcode AS node_field_data_langcode, users_field_data_node_field_data.langcode AS users_field_data_node_field_data_langcode, content_moderation_state_field_data_node_field_data.langcode AS content_moderation_state_field_data_node_field_data_langcode, node_field_data.title AS node_field_data_title, node_field_data.nid AS nid, users_field_data_node_field_data.uid AS users_field_data_node_field_data_uid, content_moderation_state_field_data_node_field_data.id AS content_moderation_state_field_data_node_field_data_id, users_field_data_node_field_revision.uid AS users_field_data_node_field_revision_uid, DATE_FORMAT((DATE_ADD('19700101', INTERVAL node_field_data.changed SECOND) + INTERVAL 3600 SECOND), '%Y%m%d%H%i') AS node_field_data_changed_minute
FROM
node_field_data node_field_data
INNER JOIN users_field_data users_field_data_node_field_data ON node_field_data.uid = users_field_data_node_field_data.uid
INNER JOIN content_moderation_state_field_data content_moderation_state_field_data_node_field_data ON node_field_data.nid = content_moderation_state_field_data_node_field_data.content_entity_id AND content_moderation_state_field_data_node_field_data.content_entity_type_id = 'node'
INNER JOIN node_field_revision node_field_revision ON node_field_data.vid = node_field_revision.vid
INNER JOIN users_field_data users_field_data_node_field_revision ON node_field_revision.uid = users_field_data_node_field_revision.uid
WHERE node_field_data.title LIKE '%%' ESCAPE '\\'
ORDER BY node_field_data_changed_minute DESC
LIMIT 50 OFFSET 0
this gives
node_field_data_langcode users_field_data_node_field_data_langcode content_moderation_state_field_data_node_field_data_langcode node_field_data_title nid users_field_data_node_field_data_uid content_moderation_state_field_data_node_field_data_id users_field_data_node_field_revision_uid node_field_data_changed_minute Décroissant 1
en fr en en 240 1 168 1 201802131758
fr fr en fr 240 1 168 1 201802131758
en fr fr en 240 1 168 1 201802131758
fr fr fr fr 240 1 168 1 201802131758
en fr en en 240 1 168 1 201802131758
fr fr en fr 240 1 168 1 201802131758
en fr fr en 240 1 168 1 201802131758
fr fr fr fr 240 1 168 1 201802131758
Is it possible to set the admin/content view to display properly the moderation state and the user that made the revision without having these duplicates?
Comment #2
matoeil commentedComment #3
leisurman commentedI have the same issue. https://www.drupal.org/project/drupal/issues/2977276#comment-12709628
Comment #10
quietone commented@matoeil Thank you for reporting this problem. We rely on issue reports like this to improve Drupal core.
Has this been resolved?
I am wondering if this has been fixed by #2977276: Node views integration that joins revisions to the default entity fails to consider langcode, resulting in duplicate rows. There has been no discussion here for 5 years, and all before the other issue was committed.
If not, provide complete steps to reproduce the issue (starting from "Install Drupal core"). Thanks!
Since we need more information to move forward with this issue, I am setting the status to Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #11
quietone commentedThere has been no confirmation that this problem still exists. Therefor, closing.
If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").
Thanks!