2.2.6

Changelog

• Fixed a problem that caused errors when placing blocks that contained date fields via IPE. (Issue #2825028)
• Fixed a problem with CKEditor caused by a bug in the new Lightning Scheduler. (Issue #2929997)
• Lightning and Lightning Project no longer override the default location of Composer's "bin" directory. (Issue #2927504)
• Made the Moderation History view compatible with Content Moderation. (Issue #2930288)
• Added a Console command that will return the current version of Lightning in SemVer format. (GitHub #543)
• Upadated the following modules:
  • DropzoneJS
  • Media Entity (Only used by sites that have not migrated to core Media.)
  • JSON API
  • Simple OAuth
  • Video Embed Field

Update Steps

Run drush updatedb && drush cache-rebuild, or visit update.php, to perform automatic database updates. You can also use Drupal Console's update:execute command.

You can then use Drupal Console to automatically run Lightning configuration updates:

$ drupal update:lightning CURRENT_VERSION

...where CURRENT_VERSION is the version of Lightning you're currently using, in semantic version format (e.g., "8.x-2.24" should be "2.2.4", and "8.x-2.21-beta3" is "2.2.1-beta3").

To run all available configuration updates without any prompting, use:

$ drupal update:lightning CURRENT_VERSION --no-interaction

Known issues

Media

• If you upload an image into an image field using the new image browser, you can set the image's alt text at upload time, but that text will not be replicated to the image field. This is due to a limitation of Entity Browser's API.
• Some of the Lightning contributed media module listed above might not yet be compatible with the Core Media entity.
• Using the bulk upload feature in environments with a load balancer might result in some images not being saved.