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.


  • Perform custom actions when the nodes expire
  • Granular permissions: let only some users to modify the node expiration date
  • Date field can use jQuery Date Popup widget, if Date module is installed with Date Popup enabled
  • All data exported to Views, if enabled
  • Drupal code compliance

This module requires Rules module.


smthomas created a great video introduction to the module on


Node expire extras module contains the following extras for Node expire.

  • "Update expiry date" Rules action. Configuration is located at
    "Structure -> Content types -> {Your Content type} -> Publishing options".
  • Tokens support. Tokens [node:expiry] and [node:expired] are available.


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

  • Expiry date format is configurable. Also it can contain date and time. Configuration is available via Configuration -> Workflow -> Node expire -> Format of expiry date. For example, formats like 10/18/2015 18:22 (m/d/Y H:i) or 25-05-2015 (d-m-Y) can be used. Hence, the branch has fixes for #979800: Date format and #366475: Date and time instead of just date?.
  • Rules module is no longer a requirement. It is possible to configure some basic actions directly without Rules module usage. Just go to admin/structure/types and configure the node type under the Publishing options -> Node expire -> Action to do. Possible actions are:
    • None (do nothing).
    • Invoke Rules event (with Rules module installed).
    • Node publish.
    • Node unpublish.
    • Make node sticky.
    • Make node unsticky.
    • Promote node to front page.
    • Remove node from front page.
  • The module has been completely rewritten in object-oriented Drupal 8 style. This is an intermediate stage for Drupal 8 module version. For Drupal 8 OOP (Object Oriented Programming) style in Drupal 7 version X Autoload module >=7.x-5.0 is required.

7.x-1.x branch can be upgraded to 7.x-2.x, but not vice versa. Shift back is not recommended, because some content type date settings can be lost - in 7.x-2.x they have more advanced format in order to keep date and time.

Please test the 7.x-2.x version on non-production sites first.

Both versions 7.x-1.x and 7.x-2.x are in good shape. 7.x-2.x is in yellow color just for not to force to update people, who are OK with 7.x-1.x. If it's not broke, don't fix it. But all new development is in 7.x-2.x.

Project Information