Hi,

I've created a patch that integrates Hierarchical Select with Features.

The patch uses the export/import Hierarchical Select configurations management and doesn't modify the behavior of the code.

Features allows you to export your module definitions to code, so that they can be imported in other drupal installations, compared, synchronized or updated.

CommentFileSizeAuthor
hierarchical_select-features-integration.patch4.45 KBsmartinm

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Did you consider instead using the Ctools export and export_ui functionality for this?

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Needs review » Postponed (maintainer needs more info)

@nedjo: is that the best practice approach to implementing Features support?

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Postponed (maintainer needs more info) » Fixed

Due to lack of response, and better some Features integration than none at all, I decided to commit this patch. Thanks, smartinm! :) (I only fixed some Drupal coding style issues.)

http://drupal.org/cvs?commit=495508

Status: Fixed » Closed (fixed)

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

shiraz dindar’s picture

shiraz dindar
Location Sooke, BC
commented

hi guys,

this patch featurizes hierachical selects but uses their IDs which are not unique across sites. by not using UUIDs for hs's, this code does not work for example, if you have a site that has a couple HS's already, and you try deploying the feature with HS's in them. correct me if i'm wrong. proper featurizing would normally require the use of machine_names instead of a site-specific ID. this is what Nedjo is getting at.

just a heads up... i would think this is better removed from the dev line for this reason.

shiraz