The "BEF Test Content" feature has the "body" field field_base. This creates a conflict with our feature which also has the body field_base.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

broeker’s picture

We have this same issue, and posted about it in the Features queue so far with no response:

https://drupal.org/node/2193391

We also now have an "Events" feature, and found the same BEF conflict with "field_date". If you read through the various related issues in the Features queue, it seems like there really is no good solution for this with the new method of declaring field_base and field_instance. It is unfortunate that a disabled "test" feature would cause conflicts with unrelated enabled Features.

This particular conflict could be solved if the BEF Test Content used some custom field names such as "field_bef_body" and "field_bef_date" . . . but the larger issue doesn't seem like it will be solved anytime soon.

mikeker’s picture

Wow... So even disabled features can conflict with existing field_base definitions? Can you confirm that is the case before I go renaming all the fields in BEF Test Content?

Thanks.

rrrob’s picture

I can confirm. I did not have it enabled, and it did indeed conflict with other features with the same base fields.

mikeker’s picture

Status: Active » Postponed (maintainer needs more info)

I just realized that I left out the hidden = TRUE in the BEF Test Content info file. (Commit: #475b11a)

Can you pull the latest -dev release and let me know if that fixes this issue?

Thanks.

idebr’s picture

Status: Postponed (maintainer needs more info) » Active

I just realized that I left out the hidden = TRUE in the BEF Test Content info file. (Commit: #475b11a)

Can you pull the latest -dev release and let me know if that fixes this issue?

Thanks.

I tested my feature with the -dev version of better_exposed_filters. The feature is hidden in Features overview, but my features still reports a conflict 'Conflicts with: bef_test_content (Disabled) in field_base [body]'

Christopher Riley’s picture

I am also seeing the conflict with the latest dev.

joelpittet’s picture

@mikeker Same as #5 and #6 still shows up even when hidden.

quimic’s picture

Same here. Conflict in features.

mikeker’s picture

Status: Active » Fixed

Apologies for not updating this issue when it happened (9 Oct), but all the field definitions in the BEF Test Content feature have been renamed to include a bef_ prefix.

@quimic: make sure you're looking at the latest -dev or the recently minted 3.0 release. Thanks.

idebr’s picture

@mikeker Could reference the issue number in the commit message when adding code to the repository, so the link is added on the issue page?

Relevant commit:

quimic’s picture

@mikeker
Indeed, v3.0 no longer creates any conflict in features. Thanks!

Status: Fixed » Closed (fixed)

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

joep.hendrix’s picture

Version: 7.x-3.0-beta4 » 7.x-3.x-dev
Status: Closed (fixed) » Active

I think this slipped back in again. In the info file there is still a features[field_base][] = body line.

Thanks for this fine module!

mikeker’s picture

Status: Active » Fixed

Grrr... Sometimes I hate Features...

  • mikeker committed 2cc836c on 7.x-3.x
    Issue #2199933: BEF Test Content feature conflicts with other feature (...
joep.hendrix’s picture

Telle me about it..
Thanks for the quick follow up!

Status: Fixed » Closed (fixed)

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

steveoriol’s picture

I confirm, if you delete the ligne "features[field_base][] = body" inside the info file "better_exposed_filters/tests/bef_test_content/bef_test_content.info", there is no more "feature conflicts".

EmanueleQuinto’s picture

Status: Closed (fixed) » Active
FileSize
3.39 KB

Sorry to reopen but it turned out there is a conflict in taxonomy as location vocabulary is not prefixed.

Please find attached the patch.

mikeker’s picture

Status: Active » Fixed

Good catch and thanks for the patch, @EmanueleQuinto.

+++ b/tests/bef_test_content/bef_test_content.info
@@ -28,7 +28,7 @@ features[field_instance][] = node-bef_test-field_bef_test_location
-features[taxonomy][] = location
+features[taxonomy][] = taxonomy-bef_test-location ¶

Removed trailing whitespace on commit.

Status: Fixed » Closed (fixed)

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