There are several tasks in the Commons installer where configuration is made without the various benefits of Features.

For example, drupal_commons_config_vars() sets variables, when these could easily exported with Strongarm + Features.

Let's look at these tasks and see which ones would be worth refactoring as Features exports.

Comments

mstef’s picture

mstef CreditAttribution: mstef commented

These were originally done like this, because we wanted variables set by default as per our "suggestion". These are variables that we expect admins to change, so we didn't want them in Features, because changing them would result in Features being overridden, and reverting features would obviously revert these as well.

Hope that makes sense..

ezra-g’s picture

ezra-g CreditAttribution: ezra-g commented

Couldn't you just put them in a non-required feature?

mstef’s picture

mstef CreditAttribution: mstef commented

I suppose you could - but that seems weird (to me). I don't see any harm in setting a few initial defaults this way, but that's just my take.

lsolesen’s picture

lsolesen CreditAttribution: lsolesen commented
Version: » 6.x-2.x-dev
Issue summary: View changes
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.