When I convert nodes I get the following errors:

Warning: array_flip() [function.array-flip]: Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->load() (line 178 of /var/www/vhosts/machines7/includes/entity.inc).

Notice: Trying to get property of non-object in file_field_presave() (line 221 of /var/www/vhosts/machines7/modules/file/file.field.inc).

Notice: Undefined property: stdClass::$uri in file_save() (line 575 of /var/www/vhosts/machines7/includes/file.inc).
Caught exception: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '' for key 2

The conversion seems to work properly though.

I don't see these messages at any other time.

The content types being converted are pretty simple and have the body field, 1 or 2 text fields, a taxonomy field and an image field.

I am using:
drupal 7.0
node_convert 7.x-1.0

Also, the site was a drupal 5 site upgraded to drupal 6 and then drupal 7 (in case that matters).

CommentFileSizeAuthor
#9 node_convert.1120406.9.patch1.76 KBjamsilver
#3 node_convert-drupal_debug-1120406-3.txt1.41 MBagileware

Comments

agileware’s picture

agileware commented

This related error occurs as well:

PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '' for key 2: INSERT INTO {file_managed} (filesize, status, timestamp) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 0 [:db_insert_placeholder_1] => 1 [:db_insert_placeholder_2] => 1302238621 ) in drupal_write_record() (line 6776 of includes/common.inc).

agileware’s picture

agileware commented

Some debugging shows that the issue is cause by my image field, which is a new image field in D7 (it didn't get migrated from older drupal versions).

* The array_flip error (entity.inc):
$ids is supposed to be an array but in this case is the boolean TRUE value.

* The property of non-object error (file.field.inc):
The $file variable is boolean FALSE instead of an object because the $items array is

array(
  0 => NULL,
);

so it is loading a nothing file.

* The undefined property error (file.inc):
The $file->uri property doesn't exist because the $file object is only:

(Object) stdClass
  status (Integer) 1
  timestamp (Integer) 1302239188
agileware’s picture

agileware commented
Title: Error messages when converting nodes » Error messages when converting nodes with image/file fields
StatusFileSize
new node_convert-drupal_debug-1120406-3.txt1.41 MB

Here is a quick debug_backtrace() for each of the errors.

Each one is prefixed by filename backtrace (ie. entity.inc backtrace) so you can navigate the file a little easier.

CatherineOmega’s picture

CatherineOmega commented

I'm also having this problem, on a from-scratch D7 site, on nodes with Image/Filefield. Same error messages. Ideas?

CatherineOmega’s picture

CatherineOmega commented

I do note that EDITING the newly-converted node and then saving it results in no errors whatsoever afterwards.

topazzz’s picture

topazzz commented

Having the same issue when converting image fields. In my case the fields were empty. Here is what I got
Warning: array_flip() [function.array-flip]: Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->load() (line 178 of /includes/entity.inc).
Notice: Trying to get property of non-object in file_field_presave() (line 221 of /modules/file/file.field.inc).
Notice: Undefined property: stdClass::$uri in file_save() (line 575 of /includes/file.inc).
Caught exception: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '' for key 'uri'

vml-bsummers’s picture

vml-bsummers commented

any updates on this? I am experiencing the same issues and can confirm the same behaviors as in #5

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

I've confirmed that this bug is encountered when converting a node type that has an image field. Re-saving the node after conversion seems to fix the invalid field data.

jamsilver’s picture

jamsilver commented
Status: Active » Needs review
StatusFileSize
new node_convert.1120406.9.patch1.76 KB

The error in question seems to arise only when dealing with nodes which did not have a value for an image/file field.

The attached patch fixed it for me.

Note, in the code this error was causing an exception which was aborting the node_save process, which is having strange effects like e.g. pathauto aliases not getting recomputed for the node.

kenorb’s picture

kenorb commented

See: #1163740: PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '' for key 2: INSERT INTO {file_managed}

donquixote’s picture

donquixote commented

I have the same issue with taxonomy fields.
I save them, and the error is gone.

Debug backtrace shows that the node taxonomy field is broken. It is something like

$node->taxonomy_vocabulary_1['und'][0]['tid'] => NULL

and nothing else in that field.

Part of the stack trace:

node_view_multiple() - with the broken node as argument
field_attach_prepare_view()
_field_invoke_multiple_default()
_field_invoke_multiple()
field_default_prepare_view()
taxonomy_field_formatter_prepare_view()
taxonomy_term_load_multiple() - with array(NULL) as first argument

I think it would be preferable if node_save() (and thus, entity_save etc) would take care to clean up those broken fields, or complain that it's broken.
Apparently they just silently save the broken thing.

mikerb’s picture

mikerb commented

I had this problem too. After converting a node, if there were no entries for tags, a null value was inserted into field_tags_tid in the field_data_field_tags table. I tried using node_save() to update all the affected nodes, but it failed too because of the null values. I ended up deleting these rows in the field_data_field_tags table, which fixed the problem.

yan’s picture

yan commented

#9 seems to work perfect for me, thanks. I always got many error messages and after that the strange behaviour that was described before: Some nodes with empty fields didn't show up in taxonomy lists until I saved them. I applied the patch (manually) and after that there are no error messages and the converted nodes appear as they should.

yan’s picture

yan commented
Version: 7.x-1.0 » 7.x-1.x-dev
Status: Needs review » Fixed

I just saw that the change from #9 is already in dev, so I guess this issue is fixed.

Status: Fixed » Closed (fixed)

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

nevergone’s picture

nevergone
Primary language Hungarian
commented
Status: Closed (fixed) » Active

Drupal core patch: https://drupal.org/node/1443158#comment-6955596

nevergone’s picture

nevergone
Primary language Hungarian
commented
Status: Active » Fixed

sorry

Status: Fixed » Closed (fixed)

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