We've replicated this bug on a couple of our systems utilizing FileField Sources.

We were migrating some content types using the Export function and noticed that afterwards any sources that are checked in the FileSources section become unchecked.

Steps to recreate.

  1. Create a content type with a cck field and check some file sources for that field
  2. Export that content type with the cck field
  4. Go to manage fields and you'll see the previously checked fields are now unchecked.

Comments

dgautsch’s picture

dgautsch CreditAttribution: dgautsch commented

step 3. is a typo ignore that blank list item.

timwood’s picture

timwood
Primary language English
Location Rockville, Maryland
CreditAttribution: timwood commented

Sub.

quicksketch’s picture

quicksketch
he/him
CreditAttribution: quicksketch commented

So all you do is export the content type and then settings are lost? You don't even import it or anything?

dgautsch’s picture

dgautsch CreditAttribution: dgautsch commented

Yes all we do is export the content type that contains that field. I think it might also be worthy to note that once it's been exported if you go to the 'edit node' screen the 'File Browse Link' is still available, but in the settings all the options are unchecked.

The reason we noticed this bug is that we are also using the Insert module in conjunction with this one.

quicksketch’s picture

quicksketch
he/him
CreditAttribution: quicksketch commented
Title: Exporting FileField Unsets Enabled Sources » Exporting Content Types unsets FileField Sources and Insert Settings in FileFields
Project: FileField Sources » Content Construction Kit (CCK)
Version: 6.x-1.1 » 6.x-2.x-dev
Component: Code » content_copy.module

I've reproduced this issue, but I don't think that FileField Sources or Insert modules would be responsible for such loss of settings. This is probably an issue for Content Copy. Exporting causes a loss of both Insert and all FileField Sources settings. I find it interesting that just exporting a content type seems to save the fields.

I get this message upon export:

    * The content type Page has been updated.
    * Saved field Field A.
    * Saved field Field B.

Just by exporting all of the fields are resaved, probably missing all the settings that have been added by modules outside of CCK.

echoz’s picture

echoz CreditAttribution: echoz commented

I'm running cck v6.x-2.9 and have lived with this reproducible bug for a long time. The content type imported looses these settings as well.

Jonah Fenn’s picture

Jonah Fenn CreditAttribution: Jonah Fenn commented

Hello! We're running into a somewhat similar problem, but it's happening with the FileField Paths module and the associated Transliteration and Pathauto options that are included with this module.

The token values aren't sticking - but this is only occurring in the FileField Path settings. The tokens work in all other incidences.

What's odd is that they do show in the export code, but on import the settings that use tokens are being eliminated and all Transliteration and Pathauto settings are being reset to 0.

We're running the following:
Drupal 6.24
FileField Paths 6.x-1.4
Pathauto 6.x-1.6
Transliteration 6.x - 3.0
Token 6.x - 1.18

Any insight would be greatly appreciated.

dagomar’s picture

dagomar CreditAttribution: dagomar commented

I have the same issue, not with filesources, but with a completely different module (epsa crop). When I export the content type, all settings are lost.