Get error on node save. Error appeared only once per node.
Insert / update nodes with module "Feed import";
Notice: Trying to get property of non-object in _taxonomy_menu_nodeapi_helper() (line 487 of /var/www/new_harbinger/sites/all/modules/contrib/taxonomy_menu/taxonomy_menu.module).
Warning: array_flip(): Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->load() (line 178 of /var/www/new_harbinger/includes/entity.inc).
Warning: array_flip(): Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->cacheGet() (line 354 of /var/www/new_harbinger/includes/entity.inc).
Notice: Trying to get property of non-object in _taxonomy_menu_nodeapi_helper() (line 488 of /var/www/new_harbinger/sites/all/modules/contrib/taxonomy_menu/taxonomy_menu.module).
Warning: array_flip(): Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->load() (line 178 of /var/www/new_harbinger/includes/entity.inc).
Warning: array_flip(): Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->cacheGet() (line 354 of /var/www/new_harbinger/includes/entity.inc).
Notice: Trying to get property of non-object in _taxonomy_menu_nodeapi_helper() (line 489 of /var/www/new_harbinger/sites/all/modules/contrib/taxonomy_menu/taxonomy_menu.module).
Warning: array_flip(): Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->load() (line 178 of /var/www/new_harbinger/includes/entity.inc).
Warning: array_flip(): Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->cacheGet() (line 354 of /var/www/new_harbinger/includes/entity.inc).
Notice: Trying to get property of non-object in _taxonomy_menu_nodeapi_helper() (line 490 of /var/www/new_harbinger/sites/all/modules/contrib/taxonomy_menu/taxonomy_menu.module).
Warning: array_flip(): Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->load() (line 178 of /var/www/new_harbinger/includes/entity.inc).
Warning: array_flip(): Can only flip STRING and INTEGER values! in DrupalDefaultEntityController->cacheGet() (line 354 of /var/www/new_harbinger/includes/entity.inc).| Comment | File | Size | Author |
|---|---|---|---|
| #3 | taxonomy_menu.module-1811850-2.patch | 740 bytes | sergiu.savva |
| #1 | taxonomy_menu.module-1811850-1.patch | 603 bytes | sergiu.savva |
Comments
Comment #1
sergiu.savva commentedthis works for me
Comment #2
hles commentedComment #3
sergiu.savva commentedadded some comments
Comment #4
hles commentedDo you have information on why it would return FALSE in the first place ? Maybe if the term should not be processed (depending on the answer of the question before), it should not done silently.
Comment #5
sergiu.savva commentedIf the term has been removed and term_id remain in the node when we call taxonomy_term_load($tid) function returns FALSE
Comment #6
hles commentedFYI this fix is already part of 7.x-2.x branch.
Comment #7
sergiu.savva commentedthx
in anticipation of the new release
Comment #8
jenlamptonSaving a node on my site currently generates about 24 warnings and 24 notices (48 error messages) because of this bug. It's certainly not minor, but I'm glad that it's already been fixed in the next release. Can't wait to upgrade :)
It can be replicated by adding a taxonomy term reference field to a node where terms in that vocabulary are in the taxonomy menu. The field type should be checkboxes, and the errors will appear when the checkboxes are left unchecked. Two for each empty checkbox.
This patch prevents these errors on my pages when nodes are saved :) Thank you @sergiu.savva
Comment #9
deanflory commentedAfter updating to Drupal 7.22 yesterday, I'm now getting these errors (and a lot more from other modules). This module's project page states the 2.x version is not ready for production yet but this issue states the fix for this is in the 2.x version. Should I use v2.x?
Here's the errors I'm getting that include the original poster's error plus a few more that may be related:
Comment #10
j4 commentedUsing this patch removed the errors for me.
Thanks!
Jaya
Comment #11
leewillis77 commentedThe patch in #3 worked for us as well today - thanks sergiu.savva!
Comment #12
jenlamptonpatch in #3 works for me as well. Thanks all!
Comment #13
japo32 commentedthanks. #3 worked for me as well.
Comment #14
dstolCommitted to both 7.x-2.x and 7.x-1.x. Thanks!