Hello,

It looks like storage_api doesn't export the storage class for a field in features.

Here's what I see in a feature file:
'settings' => array(
'default_image' => 0,
'storage_class' => array(
'class_id' => '2',
'current_class_id' => '2',
),
'uri_scheme' => 'storage-field-cast-image',
),

This is using a class_id, which can change between environments. It doesn't look like there's a way to export the class with the feature.

Thanks,
Eric

Comments

paulmckibben’s picture

paulmckibben
he/him
Primary language English
Location Atlanta, GA
commented

I would love to see the storage classes and containers exportable in a feature. Any chance this can happen?

dwatts3624’s picture

dwatts3624 commented
Issue summary: View changes

+1 on this. Our dev team would be open to helping with this with some direction.

Andre-B’s picture

Andre-B
Primary language German
Location Offenburg, Germany
commented

@dwatts3624 https://drupal.org/node/928026 might be a head start for getting stuff exportable. But I am not that deep into storage_api to help you further.
edit: wrong link.

Andre-B’s picture

Andre-B
Primary language German
Location Offenburg, Germany
commented

@dwatts3624 has there been any progress so far?

jiv_e’s picture

jiv_e commented
Related issues: +#2325149: Allow configuration management through settings.php
PatchRanger’s picture

PatchRanger commented
Version: 7.x-1.5 » 7.x-1.x-dev
Component: Miscellaneous » Code

May be it is better to turn Storage API models into entities (https://www.drupal.org/project/entity)? It will automatically (as far as I understand it) make them exportable via Features.

perignon’s picture

perignon commented

A lot of work is necessary to improve the exportability of Storage API. To do this, we will be looking at making more use of single fields in the DB tables and Drupal variables.