4

I've created a View in Drupal 6 with Views 2. If I want to get this view from my dev site to production, is there a compelling advantage offered by using Features over using the built-in Views export?

9
  • 2
    You might also want to check out Configuration, Features doesn't hold a candle to it for config management in my opinion
    – Clive
    Nov 16 '12 at 15:17
  • That looks really useful, but I'm using Drupal 6.
    – beth
    Nov 16 '12 at 15:23
  • 1
    @Clive Whilst we're mentioning config management, I'm just gonna leave this here: Configuration builder.
    – Chapabu
    Nov 16 '12 at 15:37
  • 1
    @beth To be fair, a lot of things will probably break/not work as expected if upgrading from D6 to D7 anyway. There's a post here about upgrading Features from D6 to D7. Consensus sees to be consolidate features into database prior to core upgrade
    – Chapabu
    Nov 16 '12 at 15:42
  • 1
    I think that Chapabu and Clive should write up alternate answers based on Configuration and Configuration Builder and outline why they may be better solutions that Features for this case.
    – mpdonadio
    Nov 16 '12 at 20:13
8

For a single View, there is no difference in functionality really. The view will be the same regardless.

I use Features anyway because it's makes it more conventient to organize multiple pieces of configuration into "features". I'm not aware that ctools offers any easy way of doing "This view with that panel and those three dependencies in one module". That is what features adds on top of Ctools.

It's worth mentioning that the Configuration module is an useful alternative that largely makes the configuration tracking easier. If you don't care about the features aspect of features, take it for a spin. (Thanks Clive for pointing this out)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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