This may be related to #854450: Recreating features with beta8 creates conflicts on features[views_api][] = "api:2" , but seems more like a new bug.

Bug: if any two features share any API version (Views, Strongarm, Ctools...), they are shown as conflicting in a fresh install. If any of the features is enabled, conflict messages disappear.

Steps to reproduce:

* Start with a fresh install
* Download features, debut_article, and debut_image, and dependencies.
* Enable Features
* Go to admin/build/features

debut_article, debut_image, and features_test all show as being in conflict. When viewing the individual features, the components shown in conflict include "api:2" (Views), "strongarm:strongarm:1" (Strongarm).

The error appears to be related to the install state of Features. If you enable any of the features individually, the conflict messages disappear.

The attached Drush Make file can be used for testing.

CommentFileSizeAuthor
features_api_conflicts.make_.txt670 bytesnedjo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bsnodgrass’s picture

I am experiencing similar issues. With only a quick look at the module, at this point it looks like my conflicts are all coming from APIs which are all shared between features, each results in a conflicts with: feature_name in the UI listing of features.

As far as I know this is not causing any errors in operations of the feature components.

Transmitter’s picture

I just ran into the same issue with my own modules.
As in the linked thread http://drupal.org/node/854450 mentioned, I just needed to commenct the lines in the info file out:
// features[views_api][] = "api:2"
But it looks more like a workaround for me :-S

rv0’s picture

Same issue here.

dillonkin’s picture

1. Same issue

2. When I recreate a feature, I refresh the features page and click on the overridden button. There is no revert button within that feature.

nitrospectide’s picture

I just ran into this as well. It surprised me, because I had created a feature and incrementally added to it, and never saw the message. It wasn't until I did a fresh install when moving the feature to a new site that it came up. My feature requires Views API - api:2, and that came up as a conflict with the default "Features Tests" feature. Likewise, enabling my feature made the error disappear.

greg.harvey’s picture

+1 - you don't see it until you do a fresh install. This is definitely a problem.

DamienMcKenna’s picture

Subscribe.

greg.harvey’s picture

In fact, we have a Feature with a bunch of views in and it's "conflicting" with the Features Test feature that comes with the module because they both declare the views API to be version 2! wtf... =/

mpotter’s picture

Status: Active » Closed (won't fix)

Closing this for lack of activity. Please re-open this issue if you can reproduce it in the latest version.