Install
Works with Drupal: ^12Using Composer to manage Drupal site dependencies
Alternative installation files
Download tar.gz
205.69 KB
MD5: c8619b2fc42d06a049cfa5fe84d9692c
SHA-1: 3d525233c4246184a98c606f8ee5dfa82cf5a255
SHA-256: 39ffaeae92a49c1834b31671259341decf28ca4100a59edbba9de65ad2677c74
Download zip
216.86 KB
MD5: 7cf967c2d0f2ee01b5bde9c7d6432602
SHA-1: 7496377f10283517b09707aea077a97c265542ed
SHA-256: 1b8c7d5d03631be94238b96773006b93f31a654ccde5d96ddac7174b8949ef35
Release notes
First alpha of the 3.1.x branch, the new development line of DB Maintenance. It has the same features as 3.0.0 and differs only in the Drupal core versions it supports.
Drupal 12 only
- 3.1.x requires Drupal 12 (
core_version_requirement: ^12). - Sites on Drupal 8, 9, 10 or 11 stay on the 3.0.x releases, which continue to support those versions as well as Drupal 12.
Changes since 3.0.0
- Raised the minimum core version to Drupal 12.
- Removed the procedural hook functions and the
db_maintenance.modulefile. Hooks are implemented only in theDbMaintenanceHooksclass through the#[Hook]attribute. - Removed
db_maintenance.services.yml. Drupal core registers the hook class on its own. - The MySQL and PostgreSQL handlers call
FetchAs::AssociativeandError::logException()directly instead of checking whether they exist.
Upgrading from 3.0.0
- No configuration changes, no schema changes and no database updates.
- Rebuild caches after updating the code, because a service definition and the
.modulefile were removed. - Custom code that calls
db_maintenance_cron()ordb_maintenance_help()directly will break; those functions no longer exist.
Testing
Tested against Drupal 12.0.0-beta1 on PHP 8.5 and PostgreSQL 18. This is an alpha release for a core version that is itself still in beta.