Hi there. The current philosophy for the list of outdated content at admin/content/node/outdated is that there's no point to it if we unpublish outdated nodes immediately. However, seeing as expiration settings can be set on a per-node basis, I disagree with this. The attached patch makes several changes:

1. Show all nodes, whether published or not, on this screen
2. Add a column, 'Status', saying whether the node is published or not.
3. Remove the check in the access for this page that ensures the expiration scheme isn't to unpublish immediately
4. While I was at it, I made the title of each node in this table a link to the node, and removed the 'view' operation, in keeping with admin/content/node. This also alleviated some of the horizontal space issues this table presents.

CommentFileSizeAuthor
node_expire_admin.diff3.41 KBdmhouse

Comments

dmhouse’s picture

dmhouse commented
Status: Active » Needs review
brmassa’s picture

brmassa commented
Version: 5.x-1.2 » 6.x-1.0
Status: Needs review » Fixed

David,

thanks for your time. However, im willing to not commit it. The reason is that we can focus on integrating it with Views, which will allow users to create any type of report they want to.

You can track the progress on http://drupal.org/node/282371.

regards,

massa

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.