This page is archived
We're keeping this page up as a courtesy to folks who may need to refer to old instructions. We don't plan to update this page.
Learn how to use Features to manage configuration changes and understand the configuration change workflow in a team environment.
Goal
Use the Features contributed module to export site configuration to code.
Prerequisites
You will need the following knowledge and skills. If you need a review, check out the Additional resources section at the bottom of this page.
- Create and update features.
- Share configuration changes between developers.
Part 1: Create and save features
Create a feature for your Movie Review content type, and save it in sites/all/modules/features.
Part 2: Enable features in a new deployment
Create a brand new Drupal installation. This is a simulation of another installation on another developer's machine.
Part 3: Update configuration changes using Features
Create a new Awards field in your Movie Review content type in your original website.
Part 4: Apply configuration changes on another project
Revert all feature changes and check to see if your new Awards field has been created on the new site.
Recap
- Features can be used to export configuration changes within Drupal, and can share configuration changes within a team.
- Developers should always revert Features (
drush fra) to apply any configuration changes in the codebase. - Features must be managed with care to avoid conflicts.
- Configuration changes must always be pushed to a live environment via feature changes or update hooks. Altering configuration on the live site via the UI should be avoided.
Further your understanding
- Continue to the next lesson: Movie Project: Install a WYSIWYG Editor.
Additional resources
- Documentation: Bundling site settings using Features (Drupal.org)
- Video: Drupal Deployment with Features and Drush (Drupalize.Me)
