Blog

May 2016
We released RC4 yesterday in response to the release of Drupal 8.1.1. In addition to updating core, RC4 also includes the following:
April 2016
Release notes Update core to 8.1.0 Update all contrib modules to their latest releases Certain modules and Drupal Core will now automatically update to the latest non-breaking release as they become available for composer-based installs. 2702009 - Fixed PHP notice about undefined title index. 2695727 - Fixed an improperly namespaced hook function. 2708609 - Fixed an issue where Entity Embed did not respect the Media Library button implemented by Lightning Media. 2688427 - Implemented a fix in Entity Embed where cap
April 2016
Some webhosts won't let you run composer. Others don't give you command-line access at all. In these circumstances, you'll need to commit your dependencies to your VCS. To be clear, neither I nor the Composer docs recommend this. But if you must, these tips might help. 1. Remove everything from your .gitignore The .gitignore file that ships with Lightning Project intentionally ignores the folders that Composer uses for dependencies. You'll need to remove everything from that file with the exception of /docroot/sites/default/files line.
April 2016
Release notes Updated core to 8.0.6. We also lowered the specificity on core releases for Composer-based installs. Core will automatically update to the latest Patch Release when composer update is issued regardless of whether there is a new release of Lightning.
March 2016
In commit 6a23801 Lightning introduced a 710k (!) patch that we apply to Panels. What's more, the patch file itself doesn't live in the Panels issue queue - it actually lives in the Lightning's. I'm sure you're wondering why :)
March 2016
Beta 5 was released today with the following changes/additions:  Lightning now automatically provides responsibility-based roles for assigning permissions to users. All content types receive their own "Creator" and "Reviewer" roles, the main difference being that creators do not have the power to publish content. There is a basic "Media Creator" role for creating new media assets, and a more powerful "Media Manager" role for administrative purposes.
March 2016
Lightning provides two types of Scheduled Updates out of the box: Publish single node at certain time Publish multiple nodes at a certain time These can actually be used to schedule a change to any State defined by Workbench Moderation - not just to the Published state.
February 2016
Lightning provides an update path between releses. That means that new functionality and bug fixes are availble to existing Lightning users as they become available. These changes often require updates to configuration... configuration that is often "owned" by the Site Builder. Lightning will not attempt to automatically modify configuration that the Site Builder might have mydified herself, or that the Site Builder might rely on in its current configuration. We use the following guidelines to determine when and what Lightning updates will change.

Powered by Drupal Lightning