Skip to main content
7 events
when toggle format what by license comment
Apr 13, 2017 at 12:47 history edited CommunityBot
replaced http://drupal.stackexchange.com/ with https://drupal.stackexchange.com/
Dec 15, 2013 at 5:21 vote accept blue928
Dec 10, 2013 at 22:04 history edited Adam Balsam CC BY-SA 3.0
deleted 20 characters in body
Dec 10, 2013 at 19:32 comment added Adam Balsam Ok, so if you DO have dev/staging/prod environments set up, then typically you would adjust your content types on dev. Once you have them the way you like them, recreate the feature on dev and push that code to staging. Once it's on staging, visit the Features admin page. One or more of your features on staging should now be marked as overridden. You should revert this feature (which is a little confusing) which will update your database to reflect the changes reflected in the new feature code. If all goes well, repeat on prod. ...I'll update my answer to reflect this when I have a minute.
Dec 10, 2013 at 19:27 comment added blue928 Also, per your ".. different discussion" comment, I would definitely like to know more about that workflow including dev, staging, and production, and how Features is best integrated into that. If you have any links, please add them? Thanks!
Dec 10, 2013 at 19:23 comment added blue928 I did not have Dev or Staging before this project, no. But now, I do - dev, stage, production. I can immediately see the benefit, and I'm assuming this is why Features is so attractive? To not have to manually re-add content types and configurations for each phase? So then, in point 3 above, you mean "Yes" in that I use the UI on the dev server, and then reexport the code to be passed on to staging and production? (What I had originally meant was can I / should I add fields directly to staging / production, bypassing features altogether)
Dec 10, 2013 at 19:13 history answered Adam Balsam CC BY-SA 3.0