This project is not covered by Drupal’s security advisory policy.
What this module does
Policy-based Entity Expiration allows you to create a set of data retention/purging policies that will allow you to automatically manage large amounts of input data that must be trimmed periodically. The policies are executed on a cron basis, and may be limited to a maximum number of items per run in order to improve performance during busy periods.
How to use
Once you install/enable the module, under Structure > Entity Expiration you will have the ability to create expiration policies. If set to active, these cron-based policies will evaluate an expiration action
Expiration API
In your own module, you may create an EntityExpirationMethod under src/Plugin/EntityExpiration that provides either entity selection options, or expiration options. These allow you to create your own selection and expiration methods, such as
- Selecting only items from the previous day, quarter, or year, while ignoring older items
- Sending pre-expiration warnings.
- Evaluating whether content meets activity criteria, and expiring inactive items only.
- Moving entity information into an archive database/table
- Converting raw input data into a separate report entity (i.e. generating a daily report)
Supporting organizations:
Maintains/develops the module
Project information
Seeking new maintainer
The current maintainers are looking for new people to take ownership.- Project categories: Administration tools, Performance, Developer tools
- Created by laboratory.mike on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
