Releases for Node expire

7.x-2.x branch is released. It has the following new features:

Added fixes for the issues:
#2422507: [PATCH] When not showing expire field, fieldset still gets created
#2438025: Notice: Array to string conversion in node_expire_form_alter()

Issue #2326187: Allow the expire field to be placed in the published options regardless of the administer nodes permission Made publishing options adjustment.

Fix for the issue #2315449: Setting default expirate date with date popup enabled.

Fixes for the issues:
#2234935: Node Clone & Replicate Incompatibility
#2248227: Update expire date every time node is published

The release contains fix for the issue #2217953: Compatibility issue with Views Bulk Operations. Also default value of configuration option 'Handle content expiry' is set to 'Trigger "Content Expired" event only once when the node is expired'.

This release has an option to use Date Popup from Date module for date entry fields. In order to use it Date module with allowed Date Popup should be installed. In Node Expire configuration section "Date popups" option should be selected under "Date values entry elements". This functionality is not available in Legacy mode.

This release has a new admin configuration section which is located in "Workflow" area under the Rules module configuration section. Deletion of node_expire record on every node update has been removed.

Development branch of Node expire.

#405608 by vikramy: Default date issue
#869394 by vikramy: Drupal capitalization standard
#597210 by vikramy: Added CSS file jQuery UI
#774514 by vikramy: Improved error message.
#716852 by vikramy: Added date format YYYY-MM-DD

#426636 Bug fix.
Credit goes to arthurf, smsearcy.

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.

• 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.