Skip to content
This repository was archived by the owner on Nov 16, 2021. It is now read-only.

3.0.0

Choose a tag to compare

View all tags
@balsama balsama released this 27 Dec 18:52
· 9 commits to 8.x-2.x since this release
3.0.0
5e7167a

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.
Assets 3
Loading