We're migrating our university's website to Drupal. Wherever possible we're using Features to export config to allow us to maintain our configuration within our revision control system (Mercurial, not Git :o( .

From what I know taxonomy terms are not natively exportable by the features module (though this appears to be achievable through the Features Extra module), so I'm wondering if there is any way to efficiently migrate Workbench Access taxonomy scheme settings and active editorial sections from one Drupal instance to another, either through an extension/patch that would allow it to be done via Features, or another method?

We will ultimately find a way to push terms from one site to another, either through the Deployment module or one of the other taxonomy migration/export/import modules, so if we were able to migrate Workbench Access taxonomy scheme settings and active editorial sections using Features that would be ideal.

Thoughts?

Thanks in advance,
Pablo

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Title: Method for migrating taxonomy scheme settings and active editorial sections from one instance to another » Export scheme configurations
Category: support » feature

The scheme settings are not exportable, largely because terms are not exportable via Features.

We would need an extension or patch to perform the export. The big issue is machine_names. Note that {workbench_access} tables do use varchar for keys, so those can be treated like machine_names. I just don't know what taxonomy exports do to the ids.

Taxoman’s picture

Taxoman commented
Version: 7.x-1.0 » 7.x-1.x-dev
jeremiahtre.in’s picture

jeremiahtre.in commented

What about using uuid? At this point uuid is making a larger entrance into D8 via the Config Mgmt. Initiative, so it may be good to be thinking about it's optional support.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

I could see that working.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Issue summary: View changes

Removed incorrect assertion regarding taxonomy migration using Features. Taxonomy can be migrated, just terms that aren't migrated.

zoheir.nabavi’s picture

zoheir.nabavi commented
Issue summary: View changes

This ability to export the access settings (Including the schema, selected content types and etc.) seems to be a very important one which makes me confused why this thread is old and active. We are using features to package our workbench setup however these settings do not get exported. As we speak I am trying to implement hook_post_features_enable_feature() so in there settings gets applied, much like how it is done in workbench_access.install

Appreciate if anyone could shed some lights.