Since the update from 1.2 to 1.3, when trying to add a biblio node through DOI, PubMed or Bibtex, I get this error message :

EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 8003 of ../site/includes/common.inc).

Comments

Toki created an issue. See original summary.

toki’s picture

I have just re-installed Biblio 7.x-1.2 and now I can add a biblio through DOI, for example. No more Error screen or message.

hunterbuchanan’s picture

We're seeing the same problem. With Biblio 7.x-1.3, we see the same error when trying to add a node:

LOCATION https://web.url/node/add/biblio
REFERRER https://web.url/node/add/biblio
MESSAGE EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 8003 of /drupalroot/includes/common.inc).

Rolling back to 7.x-1.2 fixed the problem.

liam morland’s picture

Version: 7.x-1.3 » 7.x-1.x-dev

Please use git bisect to figure out which commit caused this problem.

emerham’s picture

It has to do with this git commit hash 9a284d1 for the issue #3088436: Undefined function search_index() on node save when core search module is not enabled. The biblio index node internal function added a check if the operation is an update, but didn't moved the _node_index_node($mynode) into the if logic.
Did some quick testing with a known site that was not working and this seems to get it back to a working state.

As a temporary work around just disabling the indexing of biblio items when creating/updating, add all your new items. Then you can renable the auto indexing on creating/updating as the update operation does work with this code.

emerham’s picture

Status: Active » Needs review
StatusFileSize
new503 bytes

Turns out I missed when new biblio's are created the index of the new node was not added into the search. This should fix that.

  • Liam Morland committed b040863 on 7.x-1.x authored by emerham
    Issue #3118697 by emerham, costasv: Always run _node_index_node() on...

liam morland’s picture

Status: Fixed » Closed (fixed)

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