Releases for Node Expire

New features:
* Max expiration date.

Improvements:
* Better interface when the user have the 'administer nodes' permission

Documentation:
* README.txt file now have USAGE section to describe how to use it.
* README.txt how have the CVS Id on it

Complete module rewrite.

This module allows you to set a "timer" into content nodes. When it reaches zero,
you can perform any type of action with the node, such as unpublishing it or
sending an email to the author.

All this power is possible due Rules module. On each cron, Node Expire scan for
expired content and let Rules module work with it. You can select several actions
to perform with these nodes.

If using jQuery UI module, the date field will activate a Calendar widget in order
to make the process easier and more fun.

If using Views module, all data will be exported, allowing you to build custom lists.

IMPORTANT: This module is not (YET at least) compatible with previous versions. So its only
indicated to new sites.

• Fixed bug where updating the expiration of a node and its children would fail if no parent data was found. (bug #167957)
• Fixed bug where the node parent wasn't being honored for the node being edited.
• Added optional JSCalendar integration
• Fixed minor typo preventing users from disabling book inheritance.
• Fixed typo causing only 1 expired node to be recorded as having its notification sent causing several notices to be sent out for a single expired node.
• Implemented patch #147380 by Wim Leers adding more date choices to the "Time after last update" dropdowns.
• Fixed incompatibility with pre-MySQL v4.1.1 (bug #150006).
• Minor alterations were made to the node_expire table for better performance.
• Experimental PostgreSQL support added (request #160612).
• Fixed function names for upgrader which caused node_expire not to be detected.
• Tag "!section_editlink" was returning a link to the node rather than the node edit page.
• Tag "!section_nodelink" was added to allow previous users to get the same results they were getting before.
• Minor gramatical changes were made to the settings page.
• Default sort order for the "Currently Expired Node" page was changed from Descending to Ascending.

This module allows users to either get notifications when a node hasn't been updated in x amount of time, to automatically unpublish such "expired" nodes, and/or to receive e-mail notifications and unpublish x days afterward.

Additional settings include allowing inheritance of the expiration settings from a book page to its children, renotifications (Notify user every x days before unpublishing), an email carbon copy address, and customizable email content. One can also choose specific node types that the expiration settings are allowed to be set on, as well as what defaults should be used for them.

In conjunction with book inheritance, an admin may decide who can and can't edit the expiration times while the parent book settings are still inherited.

If the admin sets the automatic unpublishing to anything but "Immediate", an additional page is available to view expired modules. ?q=admin/content/node/outdated

This module requires the use of Drupal's cron system for automatic unpublishing and email notification features.