Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We are unable to edit any cck fields because we keep receiving this error:
Invalid argument supplied for foreach() in /home/drupal_6x_prd_01/sites/all/modules/filefield/filefield_widget.inc on line 512.
It doesn't matter what field we're editing, if we select the fields to edit, and then submit them - the module reports that the processing was completed without any problems. But when we look into the logs, we see that error. It seems to prevent the actual processing to fire.
This is an issue linked to http://drupal.org/node/358617.
Comments
Comment #1
infojunkieDoes the field that you specify actually get modified in spite of this error? Please try with CCK fields and normal node fields (e.g., Published). Thanks.
Comment #2
infojunkieComment #3
EWB CreditAttribution: EWB commentedFor what is worth I get the same error but find that I am able to successfully update the content of the fields that I have edited. Note that I am updating the content of a text field for nodes with a content type that includes a cck fields that uses Filefield.
Comment #4
justindodge CreditAttribution: justindodge commentedI get the error, it is in the validation routine for the filefield submit and does cause any issues. I've tested a few simple text based CCK fields and they work fine.
I'm NOT able to get actual file field files to work by putting files into the file browser form element. This has nothing to do with the validation error mentioned above.
Comment #5
infojunkieThis issue is confusing. Closing it because the CCK Fields action has been heavily reworked since that time.
Comment #6
EWB CreditAttribution: EWB commentedFor what it is worth, I still get this error with 6.x-1.9 but can get it to disappear by using the Modify Node Fields option and selecting only those
CCK field(s) that do not use filefields. The resulting form that is presented to the user is then error free. I realize that this isn't a solution for folks wishing to modify CCK fields that are filefields but, for me, I need to modify text-based CCK fields and was/am hoping to avoid triggering the error message mentioned above.