On a sufficiently large or complex site that uses Features to export or manage configuration, it seems easy to encounter a scenario where an administrative user can inadvertently change a variable that has been "featurized" and end up having that variable reverted when features get reverted at the next code update.

The person making the change needs to remember (and to have access) to either check the Feature UI or grep the features code. I'm curious how other big sites might be handling this problem. Is there any trick to maybe highlight variables that have been featurized when they get exposed in the UI?

2 Answers 2


Try using the configuration module along with Drush. It writes the configurations into files which you can manage using GIT.

You run drush config-export –all on your dev and push your code with the config using GIT. Then you pull the changes on your prod server and run drush config-sync. It takes the config from the text files and puts them into the database making the changes live on the site.

Here is a nice article which explains this - https://shanetully.com/2014/04/drupal-and-the-holy-grail-of-workflows/


Checkout Features Builder (I work with the guy who builds this but I'm not basing this answer on that it is really a good module and used it before that).

Stop clicking together your Features

Save valuable time (and sanity) by bypassing the process of picking and choosing which components go into which Features. Features Builder is a module that analyzes the build of your Drupal site and automatically builds Feature modules to capture the site's configuration.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.