3.0.2

Changelog

• Drupal Core has been security updated to 8.4.5.

• The update:lightning command:

  • Has been ported to Drush 9.
  • Reads the previous version from config and, as a result, no longer requires nor accepts the version argument.
  • Usage:

  drush update:lightning
  # To run all available configuration updates without any prompting, use:
  drush update:lightning --no-interaction 
  

  • Note: Configuration updates from versions of Lightning < 3.0.0 will not be run when using the updated command. You should update to the last available 2.2.x release before updating to 3.x.

• All Lightning components have been updated to RC1 or greater and are no longer pinned to specific releases.

• Component updates:

  • Lightning API has updated JSON API to 1.10.0. See Lightning API's CHANGELOG for more information. (Issue #2933279 and SA-CONTRIB-2018-15)
  • Lightning Layout has fixed a configuration problem that caused an unneeded dependency on the Lightning profile. This means that Lightning Profile is now fully compatible with the Config Installer. (Issue #2933445)
  • Lightning Media now allows media types to be configured without a Source field. (Issue #2928658)
  • Lightning Workflow can now be installed without the Views module. (Issue #2938769)

• Note: This is the last release on the 8.4.x branch of Drupal Core. The next Lightning release will be 3.1.0 and will require core ~8.5.0.

Update Steps

Run drush updatedb && drush cache-rebuild, or visit update.php, to perform automatic database updates.

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.

API

• Users might have trouble interacting with certain configuration entities via the API.

3.0.1

Changelog

• Drupal Core has been updated to 8.4.4 (Issue #2934239)

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.

2.2.7

On December 27, 2017, when we released Lightning 3.0.0, the 2.x branch became unsupported and will only receive security updates. When version 8.4.4 of Drupal core came out a week after Lightning 3.0.0, we decided to do a "courtesy" release on the 2.x branch since people hadn't had much time to update.

So what this means is that Lightning 2.2.6 is functionally equivalent to Lightning 3.0.0. And Lightning 2.2.7 is functionally equivalent to Lightning 3.0.1. But we never made a 2.2.7 (8.x-2.27) release on drupal.org.

Simply put, if you're now on 2.2.7, you should switch to 3.0.1.

3.0.0

Changelog

• Lightning's components are no longer bundled with the profile. They are now packaged as separate components and located alongside other Drupal modules. (Issue #2925010)
• The following unused modules have been removed from the build manifest (Issue #2927527):
  • Scheduled Updates
  • Lighting Scheduled Updates
  • Features
  • Configuration Update Manager
  • Media Entity
  • Media Entity Document
  • Media Entity Image

Update Steps

If you use any of the modules listed above that have been removed from Lightning's build manifest, you will need to add them to your project's composer.json file or include them in your codebase some other way.

You will likely need to update Lightning's constraint to get the 3.x branch. The following is a good starting point, but additional commands might be needed depending on your specific requirements and constraints:

composer require acquia/lightning:~3.0.0 --no-update
composer update acquia/lightning --with-dependencies

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.

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.

2.2.5

Changelog

• The since option used with the update:lightning console command has been converted to an argument and is now required. See "Automated configuration updates" in the UPDATE.md file for more information.
• Drupal core has been updated to 8.4.3. (Issue #2929035)
• Security updated Configuration Update Manager module to 8.x-1.5. (SA-CONTRIB-2017-091)

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.

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.

2.2.4

Changelog

• Lightning Workflow has been updated to use core Workflows and Content moderation modules and existing sites will be migrated. (Issue #2863059)
• Added a new Scheduled Publications sub-component of Lightning Workflow which replaces Scheduled Updates (which is incompatible with Content Moderation).
• Fixed a bug where media names appeared in view modes where they had previously been hidden after updating to core Media. (GitHub #521)
• Crop API was updated to 2.x. (GitHub #519)
• Media Entity was updated to 2.x. (Issue #2927823)
• DropzoneJS was updated to 2.x (GitHub #528)
• Fixed a bug where it was possible that old, irrelevant configuration updates could be run (GitHub #531)
• Fixed a bug where Lightning's media browser enhancements could not be used on any other view, including clones of the media browser. (Issue #2905876)

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 --since=2.2.3

Or perform the following manual update steps:

• Visit Structure > Media types. For each media type, click "Manage display" and select the "Embedded" display. Then drag the "Name" field into the "Disabled" section and press "Save".
• To migrate to Content Moderation, install the wbm2cm module and Drush (8.x or 9.x). Back up your database, then run drush wbm2cm-migrate to run the migration.
• If you previously used a sub-profile to exclude Lightning Workflow's "Schedule Publication" sub-component (its machine name is lightning_scheduled_updates), you will need to update your sub-profile's excluded dependencies to exclude lightning_scheduler instead, which replaces lightning_scheduled_updates in this release.

Known issues

Media

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.

2.2.3

Changelog

• Updated to and require a minimum of Drupal Core 8.4.1.

2.2.2 to 2.2.3 Manual Update Steps

There are no manual update steps for this release.

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.
• The Video Embed Field module, a dependency of Lightning Media, might report that it is unsupported. We're working with the module maintainer to remove this warning.
• Using the bulk upload feature in environments with a load balancer might result in some images not being saved.

Workflow

• Lightning Workflow is based on Workbench Moderation, which is incompatible with the experimental Content Moderation module included with Drupal core 8.3.0 and later and serves the same purpose as Workbench Moderation. We plan to seamlessly migrate Lightning Workflow to Content Moderation once it is ready and an update path exists (see Issue #2863059 for more information). But for now, installing Content Moderation alongside Lightning Workflow may have unpredictable and dangerous effects, an is best avoided.

2.2.2

Changelog

• Lightning Media has been updated to use the new Core Media system.
• Fixed a bug where the "Publishing status" checkbox appeared on content edit forms when it should have been hidden. (GitHub #479)

2.2.1 to 2.2.2 Manual Update Steps

Special instructions for media entity migration

This release will migrate your existing media entities to the core media module. Prior to running the database updates, you must ensure Composer properly downloaded and patched all dependencies.

This release changes the set of patches that are applied to drupal/core without actually updating core, which exposes this bug in the composer-patches plugin. As a result, you will likely need to run composer update twice. Specifically:

composer update acquia/lightning --with-dependencies
composer update drupal/core

Alternatively, you can delete your "/docroot/core" and "/docroot/modules" folders and your composer.lock file before running composer update. If you use BLT, the provided composer nuke command will do that for you.

Before proceeding, you may wish to verify that Media Entity's upgrade path will work. Media Entity includes a Drush command (compatible with Drush 8.x only at the moment) to do this:

drush media-entity-check-upgrade

This will report any potential errors and allow you to correct them before you run database updates.

At this point, if your codebase has been updated properly, you should see the following four pending database updates when you run drush updatedb:

lightning_api module : 
  8002 -   Installs the Consumers module. 

lightning_media module : 
  8018 -   Updates the media browser's argument validation. 

media_entity module : 
  8200 -   Clears the module handler's hook implementation cache. 
  8201 -   Replace Media Entity with Media. 

Configuration updates

• Visit Structure > Content types. For each moderated content type, click "Manage form display", then drag the "Publishing status" field into the "Disabled" section and press "Save".

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.
• The Video Embed Field module, a dependency of Lightning Media, might report that it is unsupported. We're working with the module maintainer to remove this warning.
• Using the bulk upload feature in environments with a load balancer might result in some images not being saved.

Workflow

• Lightning Workflow is based on Workbench Moderation, which is incompatible with the experimental Content Moderation module included with Drupal core 8.3.0 and later and serves the same purpose as Workbench Moderation. We plan to seamlessly migrate Lightning Workflow to Content Moderation once it is ready and an update path exists (see Issue #2863059 for more information). But for now, installing Content Moderation alongside Lightning Workflow may have unpredictable and dangerous effects, an is best avoided.