Block Expiry enables site builders to schedule when blocks appear on a Drupal site. You can set start and end dates for any block, making them visible only during specific times or for a limited duration. This is useful for temporary announcements, event promotions, or time-sensitive alerts without needing cron jobs.
Block Expiry allows site builders to control block visibility based on time by adding optional start and end date fields to block configuration.
Once enabled, any block can be configured to:
- Appear only after a specified start date
- Automatically disappear after a specified end date
- Be visible only within a defined time window
If no dates are set, the block behaves normally and remains always visible.
Features
- Adds start and end date controls to all blocks
- Works with custom blocks, Views blocks, and core block plugins
- No cron dependency
- Uses proper access checking (blocks are not rendered when expired)
- Timezone-aware and cache-safe
- Compatible with Drupal 10 and Drupal 11
Typical use cases
- Temporary announcements or banners
- Campaign or event-related blocks
- Maintenance notices
- Time-limited promotions or alerts
Ask your assistant about Block Expiry
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
Releases
| Version | Type | Core | PHP | Release date | |
|---|---|---|---|---|---|
| 1.0.0-alpha1 | Pre-release | Jan 28, 2026 |