Steps to reproduce:

1. Create 2 new content types
2. Create a filefield on one of the types
3. Use that field on the other type
4. Export each type in a separate feature
5. See that there is a conflict

Issue is caused by the "filefield_paths_features_pipe_content_alter()" function blindly exporting settings without checking to see if they've already been exported.

Commenting the contents of this function out will allow you to manually set the export, which is more time consuming but probably safer overall.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

thedavidmeister’s picture

here is a patch to comment out that line for 6.x-1.x-dev

Deciphered’s picture

Heh, I was about to point out what a horribly fix that patch is, then I saw your username and remembered that I suggested the patch as a quickfix.

The real solution is to somehow check if a settings have already been exported, which in itself isn't an easy fix. Will try to look into this when I have more time.

thedavidmeister’s picture

the patch is buggy btw :P weird shit happens (I can't remember exactly what) but at least I can export things again.

Deciphered’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

No longer supporting Drupal 6 issues for this module.