Data array not unserialized on the sanitize call

Patch doesn't work for me.
I've tried to modify or create new contents, but I still get warning: unserialize() expects parameter 1 to be string

please post patches, not .gz files.

Fixed the comment. Anyone else able to test this?

After reinstalling both modules everything seems solved..
Thanks a lot!

The fix seems to solve the issue, but maybe the root of the problem is in CCK itself?

Curiously enough, CCK handles serialization transparently in content_write_record(), handling insert/update. However, it doesn't offer a similar feature on field data load. :(

CCK invokes hook_field('load') and filefield already does the unserialization in filefield_field_load(), so it seems the problem may only happen when field data is not loaded by CCK. Probably from Views? ...and this problem happens when the CCK views handler for a field invokes content_format() from the render method. Maybe that method could deal with unserialization, but that would be a CCK issue.

In cck/includes/views/handlers/content_handler_field.inc

     $item = array();
     foreach ($db_info['columns'] as $column => $attributes) {
-      $item[$column] = $values->{$this->aliases[$attributes['column']]};
+      if (empty($attributes['serialize'])) {
+        $item[$column] = $values->{$this->aliases[$attributes['column']]};
+      }
+      else {
+        $item[$column] = unserialize($values->{$this->aliases[$attributes['column']]});
+      }
     }

CCK could also handle the unserialization of field columns from content_storage('load'), and then filefield would not have to worry about it.

             foreach ($db_info['columns'] as $column => $attributes) {
-              $item[$column] = $row[$attributes['column']];
+              if (empty($attributes['serialize'])) {
+                $item[$column] = $row[$attributes['column']];
+              }
+              else {
+                $item[$column] = unserialize($row[$attributes['column']]);
+              }
             }

Well, I just opened bug report in the CCK issue queue: #364440: Inconsistent management of serialized columns

Let's see if this can be resolved in origin. If so, current code in filefield that unserializes the data could be patched to only invoke unserialize if $item['data'] is string, so it would still work with versions of CCK older than the one that could include support for unserializing in CCK itself. Well, maybe, it's just an idea.

marked #350297: Title and Alt fields display "a" when editing form as a duplicate.

went ahead and committed this to HEAD. simple fix so there's no sense in waiting for CCK.