Release notes - Lightning¶

Resolved security alert¶

• Drupal core - Moderately critical - Cross Site Scripting - SA-CORE-2019-004

Drupal core and module updates¶

• Updated Drupal core to version 8.6.13.
• Updated Lightning Core to version 3.9.
• Updated Lightning API module to version 3.5.
• Updated Consumers module to version 1.9.
• Updated Lightning Media module to version 3.8.
• Updated Entity Browser module to version 2.1.
• Updated Lightning Layout module to version 1.7.
• Updated Lightning Workflow module to version 3.5.

Changes¶

• Lightning Core no longer includes deprecated function calls.
• Website builders may now use any version of the Consumers module version 1.9 or later.
• Lightning Media now links to the settings form on the module list page.
• Lightning Media and Lightning Layout now display descriptions for administrative links.
• Lightning Workflow now replaces entity_load() calls with entity load().
• Lightning Scheduler now displays a description in links.menu.yml file.
• The following components of Lightning now support Drupal core version 8.7:
  • Lightning API
  • Lightning Layout
  • Lightning Media
  • Lightning Workflow

Fixed issue¶

• Lightning Scheduler did not display a configure button on the list page.

Resolved security alerts¶

• Drupal core - Highly critical - Remote Code Execution - SA-CORE-2019-003
• JSON:API - Highly critical - Remote code execution - SA-CONTRIB-2019-019
• Metatag - Critical - Remote code execution - SA-CONTRIB-2019-021

Drupal core and module updates¶

• Updated Drupal core to version 8.6.10.
• Updated Lightning Core to version 3.7.
• Updated Metatag module to version 1.8.
• Updated Lightning API to version 3.4.
• Updated JSON:API to version 2.3.
• Updated Lightning Media module to version 3.6.

Changes¶

• 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.
• Lightning Core now includes a Long (12-hour) date format, which formats dates and times such as April 1, 2019 at 4:20 PM.
• Lightning Core now namespaces all declared dependencies.
• The media browser packaged with the Lightning Media module now displays in a modal dialog box by default, which activates by pressing the Add media button. When embedding media in the WYSIWYG editor, the media browser remains unchanged (the entity browser used for WYSIWYG is now a separate entity browser configuration).

Fixed issues¶

• Converting descendant profiles to the Drupal 8.6-compatible format failed if the active profile, itself, was a descendant profile.
• An undefined index error displayed when processing form elements containing legends.

Resolved security alerts¶

• Acquia Connector - Moderately Critical - Access bypass - SA-CONTRIB-2019-014

Module updates¶

• Updated Acquia Connector to version 1.16.
• Updated Consumers to version 1.8.
• Updated JSON:API to version 2.1.

Resolved security alerts¶

• Drupal core - Critical - Third Party Libraries - SA-CORE-2019-001
• Drupal core - Critical - Arbitrary PHP code execution - SA-CORE-2019-002

Drupal core and module updates¶

• Updated Drupal core to version 8.6.6.
• Updated Lightning API to version 3.2.
• Updated Lightning Layout to version 1.6.
• Updated Lightning Media to version 3.5.
• Updated Lightning Workflow to version 3.3.
• Updated Moderation Dashboard to version 1.0-beta1.

Changes¶

• Lightning Core now systematically clears all persistent caches before running database updates with Drush 9.
• Website builders now have the option to not use the default media browser for newly-created media fields (such as entity reference fields which reference media items).
• For any media type, the Show in media library field packaged with the Lightning Media module cannot be translated.
• The time steps in the Lightning Scheduler module user interface are now configurable.
• All stated dependencies now display project namespaces.

Fixed issue¶

• Users and timestamps in Moderation History did not correspond to revisions.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you encounter any errors, contact Acquia Support.