EntityMalformedException: after upgrade from 7.x-1.2 to 7.x-1.3

Saw this as well and did a little debugging - the issue is that a taxonomy term is being passed around that doesn't have $term->vocabulary_machine_name set.

The term gets passed through the rendering code in entity_views_handler_field_entity before this error, which makes me think the bug is likely related to the regression being discussed in #1796110-18: Rendered entity fields show same result. Sure enough, making the code change discussed in comment #21 of that issue fixed the problem for me, but I don't fully understand the issue and I'm also seeing PHP notices after making that change, so this would need more testing to be sure it's the right fix.

EntityMalformedException: Missing bundle property on entity of type profile2. in entity_extract_ids()

This is a with a Views display of type user. (After updating from 7.x-1.2+11-dev.)

Reverting try2 and applying try1 from comment #14 in #1796110: Rendered entity fields show same result fixes this error for me, too. No idea if this is the proper fix, but patch attached for testing and reviewing.

Raising priority because these pages are completely killed.

Sorry, it was an error
comment deleted by author

3: entity-missing-bundle-property-2171689-3.patch queued for re-testing.

We ran into this on Drupal.org, #2173087: Regression: "Project" column on "Your issues" has lost its link. The patch looks good.

Confirming that the patch also fixes a problem with Views fields that are based on Entity computed properties.

#2174645: Fields using views relationships show no values (using Search API) has also been marked as a duplicate.

Looks like we choose the wrong patch variant. :-/ But great to see this has been widely tested now.

Thanks, committed.

The commit does not seem to be pushed? Also, 7.x-1.x and 7.x-1.3 are broken on d.o. bots...:

7.x-1.x: https://qa.drupal.org/pifr/test/27276
7.x-1.3 https://qa.drupal.org/pifr/test/701198

Resetting to fixed since the tests seem to be a general problem, not this particular patch.

The commit is at https://drupal.org/node/626176/commits.

For the tarballs, they can get into a situation where they do not get re-packaged if the most recent commit is made less than 300 seconds after the most recent packaging. A new commit will trigger packaging again and clear it out. #2168239: Store, and use, commit hashes of packaged projects would fix it.

>Also, 7.x-1.x and 7.x-1.3 are broken on d.o. bots...:

Yep, noticed that as well + pushed a fix.