This project is not covered by Drupal’s security advisory policy.
The Scheduled Updates module allows scheduling updates at a specific date and time to entities such as Content(nodes), Users, Terms, Files and many more. Update dates can contain 1 or multiple fields. Since many more things are fields in Drupal 8 this means you can also update properties like published, promoted, sticky, title and pretty much anything else you can think of.
This modules supports 2 different types of updates:
These updates can be embedded on the add/edit form of the entity they will be updating.
- Scheduling Publish and/or UnPublish Dates directly on node forms.
- Set a user to inactive at a certain date on the user edit form.
These updates are added directly using their own forms. When making these updates the user selects nodes, users or other entities they would like to update. These updates can target multiple entities in a single update.
- Select a group of nodes to be promoted and/or published on a certain date.
- Select a group of users to be given a Manager role at the beginning of the next month.
Before making updates you must first create at least one Scheduled Update Type.
A Scheduled Update Type:
- Can only target one entity type to update
- Can either be embedded or an independent update
To easily create embedded updates click Add Update Field on the Manage Fields page of the entity type you want to update.
To create a scheduled update type go to: Configuration -> Workflow -> Scheduled Updates -> Scheduled Update Types
After you have created a Scheduled Update Type you will then be prompted to choose the fields from your target entity type to include on your new update type.
Currently working towards an 8.x-1.0 release
- Maintenance status: Actively maintained
- Development status: Under active development
- Module categories: Utility
- Reported installs: 3,129 sites currently report using this module. View usage statistics.
- Downloads: 40,046
- Automated tests: Enabled
- Last modified: 21 April 2017
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.