You are here

Home » API reference » Auto Expire 7

README.txt in Auto Expire 7

Same filename and directory in other branches
  1. 5 README.txt
// $Id: README.txt,v 1.5 2009/06/04 23:19:37 marcvangend Exp $

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 then he can 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).


For configuration use admin/config/content/auto_expire (Configuration->Content authoring->Auto Expire)

Expire info for node appears as a tab when viewing/editing node.

File

README.txt
View source 
  1. // $Id: README.txt,v 1.5 2009/06/04 23:19:37 marcvangend Exp $

  2. 

  3. This module allows site administrators to set expiration times for content types.

  4. 

  5. End users creating content that has auto expiry set cannot control the expiry time. They

  6. could be allowed to renew the content for one or more cycles.

  7. 

  8. Before a node is expired a warning message is sent to the user that created that node. If

  9. the user has the proper rights then he can extend the node.

  10. 

  11. A node is unpublished on the first cron run after the expiry date. Nodes that have

  12. expired for a certain amount of time can be automatically purged.

  13. 

  14. This module is ideal for content that is allowed only for a limited time, like

  15. classified listings.

  16. 

  17. Somewhat similar modules are Scheduler and Node Expire. Scheduler allows the user

  18. creating the node to set the expiry time, Auto Expire enforces an expiry time set by

  19. the administrator. Node Expire allows both default settings for each node type and

  20. individual settings for nodes, content is expired based on last update time. Auto

  21. Expire is expiring content based on creation time, and content has to be explicitly

  22. extended (a simple update is not sufficient).

  23. 

  24. 

  25. For configuration use admin/config/content/auto_expire (Configuration->Content authoring->Auto Expire)

  26. 

  27. Expire info for node appears as a tab when viewing/editing node.