First: thank you for this great module! The way it is designed to work with a separate library through composer is awesome, and I'm really looking forward to all the stuff that is planned on your roadmap.

I've got a D7 setup with a fresh install of BAT (local) and just created one type bundle with a single type and one event type with three states. Now when I try and create a feature (Features 7.x-2.10) with the event type (bat_event_type) to deploy my config, the three states keep on being multiplied with every cache clear, page view, cron, etc. And so the feature stays overridden and can't be reverted and I end up with tons of states, all being copies of the three original states... Any suggestions on how to avoid this "behavior"? I don't know if it's relevant, but there's 2 more features involved: a "base-fields-feature" (with 3 field bases: event_bat_unit_reference, event_state_reference and field_availability) and one with the type bundle (bat_type_bundle). Thanks for any help!

Comments

bartramos created an issue. See original summary.

acrollet’s picture

Hi there,

haven't seen this one but we'll take a look when we're able.

  • nicola85 committed 99a7807 on 7.x-1.x
    Issue #2726921: Prevent event states duplication
    
ronald_istos’s picture

Status: Active » Needs review
bartramos’s picture

Status: Needs review » Reviewed & tested by the community

Thank you for responding so quick and accurate! I can confirm that I applied and tested this patch, and for my use case it works perfect.

acrollet’s picture

Status: Reviewed & tested by the community » Closed (fixed)