Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
So one hassle of Drupal 6 is that it’s tough to move changes from a development server to a test or staging server to a production server.
Has this been made easier in Drupal 7? Is there some coding conventions module developers are suppose to follow now. So a developer can easily separate content and configuration and only move configuration between dev, test, and prod?
Is the recommended advice to still use the Features module?
To the best of my knowledge, there are no additional features in Drupal 7 that specifically address the deployment issues. Features will probably continue to be the best solution to that set of issues, for some time. However, some of the new features in Drupal 7 such as entities and fields in core may make it easier, when creating a module, to expose its configuration data to Features.