When viewing admin/content/node, users administering sites with thousands of nodes may have problems finding required content because they need to know at least date of node creation. This patch adds "Created" column into content table. I think it fits into "usability" patches...

CommentFileSizeAuthor
content_2.patch2.44 KBmeba

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

I heard from some people that the content admin page is already two crowded, and we should keep an eye on the number of columns there (eg. display the language column in more restricted circumstances only). So it would be nice to have this reviewed by more people. I am not sure this data should be there by default.

dries’s picture

dries commented

I'm not full convinced either.

meba’s picture

meba commented
Status: Needs review » Needs work

Me neither :-)
I think this screen needs more love. My thoughts:

- Put "Show only items where" to collapsible fieldset
- Allow sorting of table items
- Add collapsible fieldset (default collapsed) with column selections? (This could be solution for all complaints)
- Add javascript stuff to table rows to allow checking the box by clicking whole <td> - allows faster selection

Which of these should be considered for D6?

dpearcefl’s picture

dpearcefl commented
Category: bug » feature

Changing to a feature request.

Is there any interest in this issue? if so, it should go to the D8 queue.

alphex’s picture

alphex commented

subscribe

This should be in D8.

KalenXI’s picture

KalenXI commented

This would be immensely useful for me. Currently only having "Date Updated" as a column in the content admin page is completely useless to me because I'm importing content from a feed so while the post date is set from the feed data and is correct, the "updated" date only refers to when it was imported not when it was added to the feed which is what I need to see.

Status: Needs work » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.