export to features

Discussing this on #drupal-commerce this morning... Here's the gist from pcambra (commerce_features maintainer) and bojanz (commerce_kickstart 2.x maintainer)

bojanz: autosku has its own storage, reads it, then alters the product type info. it is not supported by features at all

pcambra: so it's config that should be made exportable. strongarm or something?

bojanz: we create the patterns during module install. strongarm is for variables only. this is a separate table

pcambra: yeah, not sure where. ouch.

bojanz: so needs its own features integration

pcambra: then ctools exportables, but IMHO that should be in autosku module

And the example code from Kickstart ...

http://pastebin.com/QDi0XAw6

In my experience, since the autosku settings are carried around with the product type when loaded with commerce_product_type_load(), they're exported automatically by commerce_features, when you export the product type. If that's no longer the case, I'm happy to write CTools export code for the commerce_autosku table.

Personally, I'm not a big fan of using variables for storage of arbitrary entity bundle settings, but I'm certainly willing to consider it if that would make things easier.

+1 It doesn't seem that autosku settings are picked up by commerce features. I don't have the time to devote to it right now, but converting to variable to support export via strongarm would be a big plus.

Thanks for a useful module!
Derek

OK, I switched from using straight up database storage to using the CTools Export API for the storage. This means that autosku patterns can now be exported by features. I'll be rolling a new stable release in the next few days unless we find an issue with the implementation.

i just wanted add that you must have ctools bulk export enabled or features won't export the autosku pattern.

Sorry for reopening this thread.

bporter2387, CTools Bulk export isn't required, just the basic CTools module and the features module.

Hi, who knows why the option "Automatically Generate SKU" is not activated when the enable features?

> I'll be rolling a new stable release in the next few days unless we find an issue with the implementation.

So it looks like this change was committed into the dev branch on Mar 25, 2013, and there hasn't been a stable release made in the three years since.

Any chance of that actually happening at some point, rbayliss?

Yep. Thanks for the reminder. I guess 3 years is probably enough time to verify that the code is stable. Just released 7.x-1.2. It should be available shortly.