This project is not covered by Drupal’s security advisory policy.
This module allows site administrators to set expiration times for content types.
End users creating content that has auto expiry set cannot control the expiry time. They could be allowed to renew the content for one or more cycles.
Before a node is expired a warning message is sent to the user that created that node. If the user has the proper rights he can then extend the node.
A node is unpublished on the first cron run after the expiry date. Nodes that have expired for a certain amount of time can be automatically purged.
This module is ideal for content that is allowed only for a limited time, like classified listings.
Somewhat similar modules are Scheduler and Node expire. Scheduler allows the user creating the node to set the expiry time, Auto Expire enforces an expiry time set by the administrator. Node Expire allows both default settings for each node type and individual settings for nodes, content is expired based on last update time. Auto Expire is expiring content based on creation time, and content has to be explicitly extended (a simple update is not sufficient).
- Maintenance status: Minimally maintained
- Development status: Under active development
- Module categories: Content
- Reported installs: 905 sites currently report using this module. View usage statistics.
- Downloads: 12,149
- Last modified: December 2, 2014
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.