Skip to main content
drupalreleases

Use direct release data with your AI assistant.

Learn more

Scheduling

Security covered Maintenance fixes only

This module allows you to schedule content to be published at specific absolute or recurring times. It supports daily, weekly, monthly, and yearly scheduling and checks content availability at runtime without requiring a cron job. The module also integrates with Drupal's caching system for improved performance.

Allows scheduling content entities either for absolute ranges, for example to have content be published starting at a specific date in the future, or for recurring ranges, for example to have content be published on a specific weekday each week.

For recurring scheduling, content can be scheduled daily, weekly, monthly or yearly. To make this recurring scheduling less daunting for users, you start by selecting a given date range using a date range widget. If the range is applicable for a recurring schedule, you can then optionally select to enable a recurring schedule. For example, if you select a date range of 10am to 2pm on January 1 of a given year, you can then choose if you want to schedule this content daily from 10am to 2pm, on the 1st of every month from 10am to 2pm, etc.

Whether or not content is currently scheduled is checked at runtime, so that no cron job is required for this module, and the scheduling is precise to the second. The access checking is also query-aware and integrates with Drupal's caching API, so that, for example, for a list that will contain a piece of scheduled content in the future, the entire output of the view (without the scheduled content) can be cached until the very second that the content is scheduled at which point it will be recomputed and subsequently cached until the next scheduling change.

Note that Views, in particular, do not currently work with the caching logic, because Views' own cache handling is incompatible with the bubbling of cacheability metadata used elsewhere in core. This will be fixed in the future.

Note that currently the patch from #2352009: Bubbling of elements' max-age to the page's headers and the page cache needs to be applied in order for the core Page Cache to respect the cache max-age of scheduled content or pages that contain scheduled content (or may contain it in the future). Without this patch, content that should be unpublished may still be returned by a cached response, so it is recommended to uninstall Page Cache module if you cannot apply the patch.

Ask your assistant about Scheduling

Check compatibility with your Drupal and PHP version, maintenance and security coverage, from current release data. How it works

Depends on

Dependencies of the latest stable release

No dependencies recorded for this project.

Required by

Tracked projects that depend on this one

No tracked projects depend on this one yet.

Activity

Tracked releases
2
Tracked since
Apr 2026
Latest release
2 months ago
Releases (12 mo)
2 ▲ from 0
Maintenance
Active

Releases

Version Type Core PHP Release date
2.0.0-beta1 Pre-release 11 Aug 31, 2026
2.x-dev Dev 11 Apr 7, 2026