Install

Works with Drupal: ^10.1 || ^11

Using Composer to manage Drupal site dependencies

Alternative installation files

Download tar.gz 85.66 KB
MD5: 9c49ffde0ae6187551a7ff7e3c5ff329
SHA-1: 17f011850eea627cccc69c04142698c1c93e1b2d
SHA-256: 5b1c4fbaff3288396dde6c3d5b936778a016673c958c39cc6514d4005515c700
Download zip 144.47 KB
MD5: 43d404d9407b94c7dba6a0235ce63ad1
SHA-1: 6c1691f64ff72b7836b2d86f2de72e8cdf8981db
SHA-256: d85e0da4654f7b3a9b6e1750ae648f09760079f51b392a45cd0f6684b750dc27

Release notes

This release moves two long-standing submodules into their own separate projects: Events and Campaign. The `3.2.x` branch requires that these modules still be present on your site, so as to avoid any upgrade surprises for users who utilize those modules. You will see that the new, independent versions of these modules are required in composer.json. Upgrading from the 3.1 branch should be simple: a cache clear is the only installation step after letting Composer handle the module updates.

The next major release (4.x) will remove this dependency from composer to allow sites that do not utilize the specific functionality in these submodules to exclude them from their codebases. This is because it is understood that these submodules or not commonly used.

Created by: gcb
Created on: 18 Dec 2025 at 21:21 UTC
Last updated: 18 Dec 2025 at 21:21 UTC
Unsupported

Other releases