I'm using features to upgrade from Drupal 5 to 6 - exporting D6 content type configurations to a feature, then enabling the module as part of the upgrade. However I keep getting this message for various fields:

Field field_foo was not created for bar because a conflict was detected for the following properties: baz

Haven't looked into the internals of this yet but if it just means my content types are 'overridden' then would be good not to get it on places such as admin/build/modules (side note, haven't looked at how to revert a feature from drush yet, but that's next up and might fix this) - since that's somewhat confusing - I'd rather just a status report somewhere, or maybe a message via hook_requirements(). If it's not harmless, then it probably needs a stronger worded message.

Comments

pimousse98’s picture

I am getting the same thing. I used features to transfer between dev and prod versions of the site. I'm also getting an issue where the autocompletes don't work anymore (I get a popup error) and I can't change any of the views (again, popup/ajax error).

austinDev’s picture

Cleared error on module page with

drush features update myfeature

I also have a javascript error on the views page, it won't run the preview. I don't know if it is related.

Still digging into this one.

catch’s picture

Title: CCK field conflicts message » CCK field conflicts message appears in unexpected places
Priority: Normal » Minor

On my end, I re-exported the feature, than added drush revert [feature] to my script, and that solved the issue for me. However the messages are still a bit overkill imo, downgrading to minor.

yhahn’s picture

Status: Active » Fixed

This message has been removed as Features handles these sorts of conflicts and resolution much more cleanly with the new rebuild code that's been committed to 6--1.

Status: Fixed » Closed (fixed)

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