This repository has been archived by the owner on Nov 16, 2021. It is now read-only.
Releases: acquia/lightning
Releases · acquia/lightning
2.1.3
2.1.2 to 2.1.3 Manual update steps
There are no manual update steps for this version.
Changelog
- Created new DrupalConsole commands that generate and customize behat.yml configuration files for functional testing. (Issue #2812775 and GH #350)
- Fixed a bug where the media library filter was hidden when the contextual filter value was "all". (GH #352 and #354)
- Updated Panels, Panelizer, Page Manage, and CTools to stable releases. (Issue #2874521)
- Fixed a bug where Lightning could, under certain circumstances, break Drupal's configuration sync functionality. Now, when a config sync is in progress, Lightning will avoid making any changes to active configuration. (Issue #2870864)
2.1.2
2.1.1
Changelog
- Panels, Panelizer and Page Manager have been upgraded to their new (stable!)
8.x-4.x releases. These releases use the experimental Layout Discovery module
in Drupal core, and will turn off Layout Plugin upon installation. Layout
Discovery is incompatible with Layout Plugin, so do NOT install Layout Plugin
once the upgrade is complete. (Issue #2870521) - The media browser will now be filtered conditionally when used with media
reference fields, depending on which media types the field can reference.
(Issue #2869240) - Implemented an API for bulk entity creation. A UI for bulk upload media items
was implemented, then pulled due to packaging issues. A patch containing that
UI is available at
https://www.drupal.org/node/2672038#comment-12044162, and will be merged back
into Lightning when the packaging problems are fixed. (Issue #2870740) - Fixed a bug where Lightning Workflow would wrongly interfere with the Save
button when creating or editing unmoderated content types. (Issue #2867465) - Fixed a bug where uninstalling Field UI would break Lightning due to an
implicit dependency. (GitHub #340 and #327) - Search API was updated to its latest release candidate. (GitHub #334)
- Listed third-party Lightning Media integrations in the README. (GitHub #339
and #346) - Lightning now uses short array syntax in all of its code. (Issue #2867638)
2.1.0 to 2.1.1 Manual Update Steps
- To allow fields that use the media browser to filter to only the media types
accepted by the field, do the following:- Edit the Browser display of the Media view.
- Add the Bundle contextual filter, to the current display only, with
the following settings:- When the filter value is NOT available, provide a default value:
- Type: Entity Browser Context
- Context key:
target_bundles
- Fallback value:
all
- Multiple values: OR
- When the filter value IS available or a default is provided:
- Specify validation criteria: Yes
- Validator: Media bundle
- Multiple arguments: One or more IDs separated by , or +
- Action to take if filter value does not validate: Display all results
for the specified field
- Under the "More" section, "Allow multiple values" should be checked.
- When the filter value is NOT available, provide a default value:
- If the view has the media bundle as an exposed filter (most likely named
"Media: Bundle"), edit it and set the "Yield to argument" select box to
the name of the argument you just created (which will probably be "Media:
Bundle"). If you don't see the "Yield to argument" select box, clear all
caches and try again. - Save the view.