Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
DO NOT upgrade to this release without reading this page first, or you may break your site!
What's changed?
Lightning Core 6 provides no new features or functionality over Lightning Core 5. The main difference is that Lightning Core 6 removes all hard dependencies on contributed modules, so you no longer need to keep modules you aren't using.
This branch contains backwards-compatibility breaking changes. DO NOT upgrade to Lightning Core 6 without reading this page first, or you may break your site!
What's changed?
Lightning Core 6 provides no new features or functionality over Lightning Core 5. The main difference is that Lightning Core 6 removes all hard dependencies on contributed modules, so you no longer need to keep modules you aren't using.
This is the final release of Lightning Core that will work with Drupal 8.
There's nothing new here; we're just keeping the lights on. This is a courtesy release before we open Lightning Core 6, which will be fully compatible with Drupal 10, semantically versioned, and dropping deprecated code and support for older PHP and Drupal core versions.
Reverted a change which allowed this component to be installed with the Standard Drupal install profile, because it caused unexpected fatal errors due to missing configuration dependencies under certain circumstances.
Lightning Core now includes the Redirect module as a soft dependency.
The base installation profile, if available, is now displayed on the administrative status report page, and via drush core:status --field=base-profile.
Lightning Core now supports attaching pictures to user accounts, and includes
a Compact display which displays the user's picture and name, both optionally
linked to the user's profile. (Issue #3026959)
Lightning Core now includes a "Long (12-hour)" date format, which formats
dates and times like "April 1, 2019 at 4:20 PM".
Fixed a bug where Lightning's utility to convert descendant profiles to the
Drupal 8.6-compatible format would fail if the active profile was itself a
descendant profile. (Issue #2997990)