As of beta8, when recreating features that include Views, the .info file is getting the following:

features[views_api][] = "api:2"

When multiple features contain this in their .info file, they show up as in conflict with one another. Not sure why, but it's problematic. I'm working around currently by removing this line from the .info file.

Comments

yhahn’s picture

yhahn commented
Status: Active » Postponed (maintainer needs more info)

Hm, the only way you would have such a key in your info file is if the feature was created with Features dev... and I can see such a feature being deployed on an older version of Features causing problems.

Are you sure the Feature wasn't made on a very recent version of Features and then deployed on an older version?

jonskulski’s picture

jonskulski commented

Young,

Sounds like it. our features life cycle as follows:

beta5
dev (API.txt/1.1.2.4)
beta8

with most features created with beta5, some in the -dev branch (can't confirm, but probably) and everything running on beta8.
Josh has found that removing that line seems to be a solution and doesn't seem to have any other issues.

yhahn’s picture

yhahn commented
Assigned: Unassigned » yhahn
Status: Postponed (maintainer needs more info) » Active

I've actually found a problem with the hook_features_api declaration that will affect -dev as well here... Will fix shortly. As mentioned above, the next version of Features will alter the Views exports slightly so you'll eventually want all of your sites up to date when the release happens.

yhahn’s picture

yhahn commented
Status: Active » Fixed

Fixed with http://drupalcode.org/viewvc/drupal/contributions/modules/features/inclu...

Status: Fixed » Closed (fixed)

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

Anonymous’s picture

Anonymous (not verified) commented

I just encountered this error again.

I created a feature with -beta8 and installed it on a new site using features-rc1. Commenting out the line in the .info file made the conflict go away.

Thoughts?

transmitter’s picture

transmitter commented
Version: 6.x-1.0-beta8 » 6.x-1.0

That's weird .. it happens for me as well.
With strongarm api and the views api - everything in a brandnew installation with the 6x10 version.
I just created my features and wanted to enable them into a fresh install and then it ran into this problem.
Commenting out the lines:
// features[ctools][] = "strongarm:strongarm:1"
// features[views_api][] = "api:2"
made it.
But why does the feature module create those lines, if it can't handle them?
Or did I do sth wrong?