I'm not sure if this is a bug or a feature request.
If you update a node and set that checkbox to flag the translations as outdated, the status of the other translations is changed to "published - outdated". But this is only visible in the "Translate" tab of that node (e.g. /node/10/translate). It would be good if the "outdated" marker would also be shown in the content overview table at '/admin/content/node'.

CommentFileSizeAuthor
#9 Picture1.png33.66 KBsteinmb
#5 node-admin-translation-status-nitpick.patch1.72 KBximo
#3 node-admin-translation-status.png46.15 KBdropcube
#3 node-admin-translation-status-207598-3.patch1.75 KBdropcube

Comments

dropcube’s picture

dropcube commented
Assigned: Unassigned » dropcube
Category: bug » feature

Ok, I am working in a patch to provide this feature

dropcube’s picture

dropcube commented
Title: outdated marker only visible at /node/x/translate » Translation status in node overview administration page
dropcube’s picture

dropcube commented
Component: translation.module » node.module
Status: Active » Needs review
StatusFileSize
new node-admin-translation-status-207598-3.patch1.75 KB
new node-admin-translation-status.png46.15 KB

The patch adds the translation status to the nodes overview in the content administration page.

An outdated mark is added to nodes flagged as 'outdated' when the source was updated significantly .

To test you should have enabled locale and translation module and configure at least one content type with multilingual support and translations. In the translation settings of the source node check "Flag translations as outdated".

There is also attached a screenshot

Do you guys have any suggestions ?
Do you think it is Ok in this way or would be good to create a column in the table for the translation status ? (I mean the nodes overview table, not a database table)

yojoe’s picture

yojoe commented

Do you think it is Ok in this way or would be good to create a column in the table for the translation status ? (I mean the nodes overview table, not a database table)

I don't think a dedicated column for the translation status is necessary. Looking at your screenshot, I think it's good this way.

Looking at your patch, I noticed that you also introduced the 'source' attribute to that table in the language column. Good. But it would be good (necessary?) to have a filter option for the 'source' property. Imagine you have thousands of nodes, then there would be certainly use cases, where you would like to filter only for the source nodes.

ximo’s picture

ximo commented
StatusFileSize
new node-admin-translation-status-nitpick.patch1.72 KB

Sounds like a reasonable addition to the node overview admin page. I agree that a column for the translation status wouldn't be necessary.

<nitpicking>You could remove the - before outdated, so that it's consistent with updated in the Title column. I took the liberty..</nitpicking>

+1 from me

dropcube’s picture

dropcube commented

ximo: Not sure about this. I used the - to separate the language from the translation status. Without the -, seems that is the language which is outdated, and not is the language, is the translation status, so are two different related properties of the nodes, for this reason the separation with -.

Again, what do you guys think about ?

yojoe: Yes, that would be good and useful to have filters related with the translation status, but this is a different feature request. I have created a new issue Translation status filter in node admin page. the patch there is ready to reviewed.

yojoe’s picture

yojoe commented

I used the - to separate the language from the translation status. Without the -, seems that is the language which is outdated, and not is the language, is the translation status, so are two different related properties of the nodes, for this reason the separation with -.

Hm, is it possible to mark a language as outdated? I think in this context it's obvious for everybody that the translation is outdated.

dropcube’s picture

dropcube commented

I think in this context it's obvious for everybody that the translation is outdated.

Yes, I just want to separate two properties of the node, the language and the translation status.

Let's see what others say ;)

steinmb’s picture

steinmb commented
StatusFileSize
new Picture1.png33.66 KB

Hi
We need to look on how the list wraps on screens with lower resolution. This is Garland on a 1024x768 screen with left and right sidebar active.
+1 on dropping the "-".

--
Stein Magne

pancho’s picture

pancho
Location UTC+2 🇪🇺 EU
commented
Version: 6.x-dev » 7.x-dev

Moving feature requests to D7 queue. Sorry...

mattie-1’s picture

mattie-1 commented

i vote for keeping the - or some other means for making the distinction clear

meba’s picture

meba commented

This looks OK for me. And splitting the text to two rows on 1024x768 seems acceptable...

robin monks’s picture

robin monks commented
Status: Needs review » Needs work

Code doesn't apply to HEAD. Please re-roll.

Robin

dan_metille’s picture

dan_metille commented

Is this patch still actual? Or is there another method for listing outdated translations?

Thanks for any information.

steinmb’s picture

steinmb commented
Version: 7.x-dev » 8.x-dev

Hi
As far as I know it did not, so until further there modules that expand translation management like http://drupal.org/project/translation_management.
Moving issue to D8

Anonymous’s picture

Anonymous (not verified) commented

What about, if the outdated mark is a link to the node translation page ??

xjm’s picture

xjm
she/her
Primary language English
commented
Component: node.module » node system
Issue summary: View changes

(Merging "node system" and "node.module" components for 8.x; disregard.)

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

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.

Version: 8.8.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. 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.

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

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

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.

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

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.

Version: 9.5.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. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Needs work » Closed (outdated)

The outdated status is available as a field on the Content view, /admin/content.