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 Media 5 provides no new features or functionality over Lightning Media 4. The main difference is that Lightning Media 5 removes all hard dependencies on contributed modules, so you no longer need to keep modules you aren't using.
This release adds full compatibility with Drupal 10, and allows sites to use Views Infinite Scroll 2.x if they choose.
Additionally, the following release notes from 8.x-4.8 apply:
This release drops support for Drupal 8.8 and older and removes the dependency on JavaScript libraries being installed from Asset Packagist. The following dependencies are removed:
This release drops support for Drupal 8.8 and older and removes the dependency on JavaScript libraries being installed from Asset Packagist. The following dependencies are removed:
This branch contains backwards-compatibility breaking changes. DO NOT upgrade to Lightning Media 5 without reading this page first, or you may break your site!
What's changed?
Lightning Media 5 provides no new features or functionality over Lightning Media 4. The main difference is that Lightning Media 5 removes all hard dependencies on contributed modules, so you no longer need to keep modules you aren't using.
Swapped out the dependency on bower-asset/dropzone in favor of npm-asset/dropzone due to build issues in the Bower version which broke bulk upload functionality.
Swapped out the dependency on bower-asset/dropzone in favor of npm-asset/dropzone due to build issues in the Bower version which broke bulk upload functionality.
Fixed bugs introduced in Lightning Media 4.0 that could occur when updating from very old versions of Lightning.
Deprecated the dependency on Views Infinite Scroll. It will NOT be included in Lightning Media 5.0, so if you need to continue using it in your project, you will need to add it to your composer.json. For example: composer require drupal/views_infinite_scroll:^1.6.
The image browser has been split into its own separate view, called "Image Browser". This change will not affect existing sites.
This version of Lightning Media requires Drupal 8.8 or later, and supports Drupal 9.
It is possible to update to this version from Lightning Media 3.x, with caveats...
When installed on new sites, this version of Lightning Media uses core tools in most cases -- it uses the Media Library module instead of Entity Browser for media reference fields and WYSIWYG embeds, and the core oEmbed system instead of Video Embed Field for remote videos (e.g. YouTube, Vimeo, etc.)
The media browser is now displayed in a modal dialog by default, which is
activated by pressing the "Add media" button. When embedding media in the
WYSIWYG editor, the media browser is unchanged (the entity browser used for
WYSIWYG has been split out into a completely separate entity browser
configuration in order to facilitate this). (GitHub #80)
Updated Lightning Core to 3.5, which security updates Drupal core to 8.6.6.
Added a configuration option to control whether newly-created media fields
(i.e., entity reference fields which reference media items) will be configured
to use the media browser by default. (Issue #2945153)
The "Show in media library" field is no longer translatable by default in any
media type included with Lightning Media. (Issue #3014913)
Changes were made to the internal testing infrastructure, but nothing that
Added a new component, Media Slideshow, which allows you to create slideshows and carousels of assets from your media library using the
Slick JavaScript library. (#52)
Lightning Media now has the Media Library module as an explicit dependency.
In Quick Edit, it's now possible to remove images selected with the media browser. (#53)