2.2.1

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.0 to 2.2.1 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:

1. Ensure Composer properly downloaded and patched all dependencies.
2. Rebuild Drupal's caches.

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.

Once you have confirmed that your codebase has been update properly, you must rebuild your site's caches before running the database updates.

drush cache-rebuild

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.

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.1-alpha2

Changelog

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

Manual update steps

• Prior to running database updates, you will need to rebuild Drupal's caches in
  order for the Media update to run properly.
• 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".

2.2.1-alpha1

Changelog

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

Manual update steps

• Prior to running database updates, you will need to rebuild Drupal's caches in
  order for the Media update to run properly.
• 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".

2.2.0

Changelog

• Lightning has been updated to run on and now requires Drupal Core 8.4.x.

2.1.8 to 2.2.0 Manual Update Steps

There are no manual update steps for this release.

2.1.8

Changelog

• Added the ability to easily crop images contained in media entities and use the cropped version when embedding or selecting the media item. (Issue #2690423)
• Lightning Media now includes a bulk upload form that allows you to create multiple image media entities at once. (#2672038)
• You can now run Lightning's manual update steps via an interactive Drupal Console command. (GitHub #462)
• OAuth key pairs:
  • Lightning will no longer try to guess where keys should be stored and won't generate the keys until an administrator triggers that action. (GitHub #445)
  • Key pairs are now generated with 600 permissions. (GitHub #443)
  • Better error messages are shown if the system encounters an error when generating OAuth key pairs (GitHub #440)
• Lightning no longer patches Drush and therefore has no opinion about which version of Drush you use in your project. (GitHub #459)
• Page manager is no longer included in the codebase. (GitHub #466)
• You can now choose to hide the links to API docs shown on entity bundles via a config option. (GitHub #435)
• Fixed a bug where Entity Browser filters might not work after updating to core 8.3.7. (GitHub #441)
• Operations is now the last column on the admin/content view. (GitHub #429)

2.1.7 to 2.1.8 Manual Update Steps

Lightning now provides a Drupal Console command to automate Manual Update steps. To interactively apply the updates, run the following command after performing the standard database updates via:

drupal update:lightning

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

drupal update:lightning  --no-interaction

If you'd rather do the updates manually, follow the instructions below.

• Lightning now ships with support for image cropping, using the Image Widget Crop module. To use it for the Image media bundle (the default behavior in new Lightning sites), do the following:
  • Install the Image Widget Crop module.
  • Visit Structure > Media bundles. For the Image media bundle, choose "Manage form display".
  • If the Image field is enabled, set its widget type to "ImageWidget crop", and configure it like so:
    • Only "Freeform" should be selected for "Crop Type".
    • "Always expand crop area" should be checked.
    • "Show links to uploaded files" should be checked.
    • "Show Remove button" should be checked.
  • Press "Update", then "Save".
  • Go to the "Media browser" tab. If the Image field is enabled, set its widget type to "ImageWidget crop" and configure it like so:
    • Only "Freeform" should be selected for "Crop Type".
    • "Always expand crop area" should be checked.
    • "Show links to uploaded files" should NOT be checked.
    • "Show Remove button" should NOT be checked.
  • Press "Update", then "Save".
  • By default, Image Widget Crop uses a CDN-hosted copy of the Cropper JavaScript library. Lightning includes a copy of Cropper as well, which you can use instead of the CDN-hosted version if you prefer to. To use Lightning's included copy of the library, visit *Configuration > Media > ImageWidgetCrop setting and make the following changes under "Cropper library settings":
    • Set "Custom Cropper library" to
      libraries/cropper/dist/cropper.min.js.
    • Set "Custom Cropper CSS file" to
      libraries/cropper/dist/cropper.min.css.
• Lightning now has support for bulk uploading media assets. To enable this feature, install the Bulk Media Upload module from the Lightning Package.
• New installs of Lightning that include the Workflow component will now place the Operations drop-button as the last column of the /admin/content view.
  To make this change in your existing Lightning installation, edit the content view, move the Operations field to the end of the list of fields, and save the changes.

2.1.7

2.1.6 to 2.1.7 Manual Update Steps

• IMPORTANT! Page Manager is no longer a dependency of Lightning Layout,
  and it will no longer ship with Lightning as of the next release. Therefore,
  if you are actively using Page Manager, you must add it to your project as an
  explicit dependency in order to continue to using it. Otherwise, you must
  uninstall it before updating to the next version of Lightning, or your site
  may break.
• IMPORTANT! Lightning has added support for pulling front-end JavaScript
  libraries into your project using Composer, via Asset Packagist.
  This requires a few simple, one-time changes to your project's root
  composer.json. Note that, without these changes, some functionality in
  future Lightning releases will not work. The required changes, and
  instructions on how to make them (either manually, or automatically using a
  Lightning-provided script) are documented here.
• Lightning now supports exposing all Drupal entities as JSON, in the standard
  JSON API format. To enable this feature, install the Content API module from
  the Lightning package.
• If Lightning's content role functionality is available, grant all "creator"
  content roles the following permissions, as desired:
  • Toolbar: Use the administration toolbar
  • Quick Edit: Access in-place editing
  • Contextual Links: Use contextual links

Changelog

• Security updated Drupal core to 8.3.7.
• Updated Entity Browser to 1.1.
• Lightning has a new top-level component called Content API. This component is installed by default and exposes all entities in your site in the machine-consumable JSON API format. This makes Lightning friendlier to decoupled applications, and allows it to be used as a backend for such. As part of this feature, Lightning now includes the JSON API, OpenAPI, and Simple OAuth modules, with basic default configuration. (GitHub #423, #421, #424, #433, and Issue #2896267)
• Lightning now supports bringing in front-end JavaScript libraries with Composer, via Asset Packagist. To take advantage of this in your Composer-based Lightning project, follow the instructions at http://lightning.acquia.com/blog/round-your-front-end-javascript-libraries-composer (GitHub #431)
• Lightning Core no longer has a hard dependency on the Metatag or Menu UI modules. (GitHub #418, #420 and #427)
• Lightning no longer has an implicit hard dependency on the Bartik or Seven themes. (Issue #2899017)
• Page Manager is no longer required by Lightning Layout. It is still shipped with Lightning, but is not a dependency and will be removed from Lightning in the next release. If you are using Page Manager, you must explicity include it as a dependency of your project. Otherwise, you should uninstall it as soon as possible. (GitHub #410)
• Quick Edit is no longer visible on published content when Lightning Workflow is enabled, because Quick Edit does not deal properly with forward revisions. In Lightning, you will only be able to use Quick Edit on unpublished drafts. (Issue #2894874)
• Split scheduled update functionality into a sub-component of Lightning Workflow, installed by default on new Lightning sites. (Issue #2893542)
• Panels was updated to version 4.2. (GitHub #409)
• Removed unnecessary lightning_core_entity_load(). (GitHub #406)

2.1.6

2.1.5 to 2.1.6 Manual Update Steps

This version of Lightning adds the ability to choose an image style, alt text,
and other settings each time you embed an image in a WYSIWYG editor, rather
that needing to rely on view modes. To enable this functionality:

1. As always, visit update.php or run drush updatedb to perform database updates.
2. Clear all caches.
3. Under Configuration > Content Authoring > Text formats and editors, configure the Rich Text filter format. Under "Filter settings", open the tab labeled "Limit allowed HTML tags and correct faulty HTML".
4. In the "Allowed HTML tags" text field, you should see a tag like <drupal-entity data-*>. Change it to <drupal-entity data-* alt title>.
5. Save the filter format.
6. Under Configuration > Content Authoring > Text editor embed buttons, edit the "Media browser" embed button.
7. Under "Allowed Entity Embed Display plugins", ensure that the "Media Image" checkbox is checked.
8. Save the embed button.
9. If you would like to allow authors to choose how embedded media should be displayed, go to Configuration > System > Lightning > Media, ensure that the box labeled "Allow users to choose how to display embedded media" is checked, then submit the form. If the box is not checked, Lightning will automatically choose a preferred display method (the recommended, default behavior).

Changelog

• Lightning now provides a Display Plugin for images embedded via CKEditor that allows editors to select an image style, alt text, and other settings each time an image is embedded. (Issue #2784699)
• You can now select and insert media items from a single-cardinality media browser with a double-click. (Issue #2888535)
• Added documentation about the known incompatibility between Workbench Moderation and Content Moderation. (Issue #2869257)
• Fixed a bug where Lightning Core might try to alter the value of a non-existent array key for unit tests. (GitHub #394)

2.1.5

2.1.4 to 2.1.5

There are no manual update steps for this version.

Changelog

• Drupal core was security updated to 8.3.4.
• Layout Plugin is no longer included with Lightning. (Issue #2873728)
• Lightning is now pinned to the 3.2.x line of the Drupal Extension for Behat due to an incompatibility between the latest versions of it and Behat. See jhedstrom/drupalextension#386 for more information (GitHub #389)
• Lightning now tests its bundled configuration for proper conformance to configuration schema. (GitHub #383 and #388)

2.1.4

2.1.3 to 2.1.4

There are no manual update steps for this version.

Note:
There is a known issue with Metatag version 8.x-1.1 where you might need to
clear your site's cache after updating. See Metatag 8.x-1.1 Release notes
and this related issue.

As per our Dependency Constraint Policy, Lightning doesn't pin to a specific
version of Metatag, so depending on your your setup, Metatag is likely to be
updated when you update to Lightning 2.1.4. For Composer users, we recommend
pinning to Metatag version 1.0.0. Alternatively, you can be prepared to clear
your site's cache immediately after running update.php.

Changelog

• Implemented UX improvements for media reference fields using Lightning's
  media browser -- the maximum number of items you can select will be displayed
  above the field. (GitHub #363)
• Fixed a bug where the media browser's upload widget, when used with an entity
  reference field, would not respect the media bundles that the field could
  reference. (GitHub #370)
• Fixed a bug where content types that do not use Workbench Moderation would not
  display their "Create new revision" checkbox. (Issue #2876698)
• All of the entity view and form displays bundled with Lightning now include
  region information. (GitHub #366)
• Patched Drupal core to suppress non-actionable warnings about expected
  behavior. (Issue #2878149 and GitHub #372)
• Various default configuration bundled with Lightning Media was updated.
  (GitHub #365)
• Hid the "Entity View" block provided by CTools from Panels IPE, since it was
  not compatible anyway. (Issue #2834173)
• Acquia Connector, Media Entity Instagram, Metatag, and Search API were
  updated to their latest versions. (GitHub #376)
• Patched Panels to include three UI/UX improvements. (Issue #2884163)
• Implemented a system to continuously generate configuration snapshots so that
  config schema changes made by modules can be propagated into Lightning's
  bundled default configuration. (GitHub #368)
• Implemented a safeguard to ensure that dependencies which Lightning is
  patching are always be pinned to a specific version. (GitHub #361)