You update a module, and it has either changed default config that it provides, or added new config items. You want to be able to import the new items, view the differences between the site config and the changed config, and possibly "revert" (or it may be an update) to the newly-provided default config.
You update a module, and it has either changed default config that it provides, or added new config items. You want to be able to import the new items, view the differences between the site config and the changed config, and possibly "revert" (or it may be an update) to the newly-provided default config.
There are two ways that members of the community can have a direct influence on the Roadmap for Drupal.org. These methods have existed informally in the past, but in 2016 we'd like to beta test some new ideas to make these processes more formal, consistent, and transparent. The first way is to volunteer your expertise to help with one of the existing initiatives we already have prioritized, or even to offer your expertise without a particular contribution in mind.
There are two ways that members of the community can have a direct influence on the Roadmap for Drupal.org. These methods have existed informally in the past, but in 2016 we'd like to beta test some new ideas to make these processes more formal, consistent, and transparent. The first way is to volunteer your expertise to help with one of the existing initiatives we already have prioritized, or even to offer your expertise without a particular contribution in mind.
There are two ways that members of the community can have a direct influence on the Roadmap for Drupal.org. These methods have existed informally in the past, but in 2016 we'd like to beta test some new ideas to make these processes more formal, consistent, and transparent. The first way is to volunteer your expertise to help with one of the existing initiatives we already have prioritized, or even to offer your expertise without a particular contribution in mind.
There are two ways that members of the community can have a direct influence on the Roadmap for Drupal.org. These methods have existed informally in the past, but in 2016 we'd like to beta test some new ideas to make these processes more formal, consistent, and transparent. The first way is to volunteer your expertise to help with one of the existing initiatives we already have prioritized, or even to offer your expertise without a particular contribution in mind.
The purpose of this theme is to serve as an example of all the features a theme can have. Pistachio is not intended for actual use on a site, and definitely should not be used on a production site.
The purpose of this theme is to serve as an example of all the features a theme can have. Pistachio is not intended for actual use on a site, and definitely should not be used on a production site.
The purpose of this theme is to serve as an example of all the features a theme can have. Pistachio is not intended for actual use on a site, and definitely should not be used on a production site.
This module modifies the Drupal "Updates available" email to include the information normally shown at admin/reports/updates, with links to the module updates and their release notes.