Notice : Undefined property: stdClass::$nid in node_access()

this seems to have worked for me.

works for me.

#2 op_update_should_be_create-2807275-2.patch works for me as well. Thank you.

#2 works for me as well. Should be merged into the next version. Thanks!

Just confirming that #2 works for me too. Thanks @anrikun.

Hopefully this can be merged soon.

Confirmed, works here too.

Confirming that the patch in #2 functions as expected. I no longer experience these error messages.

Patch in #2 fixed the issue on one of our production website.

#2 works for me too.

Patch #2 is working.

#2 works for me too.

Entity API is a important module on a website. Patch this module is a bad thing...
Do you think include this correction in a next version of Entity Api?

This patch works for me, too.

Yes, the patch fixes the notice. Should this bug have an automated test added to try and prevent future regressions?

Patch #2 is working for me.

hi on Drupal 7.53 patch 2 tested and applied successfully with both Phpstorm and Patch manager module.

Ran into this issue with a node type that just contained a title field and one Paragraphs field. Patch works well, thanks!

@Cottser: Maybe it's just me, but a test seems like overkill. How about a comment?

// We need to check if $node->nid is empty, since $node->is_new is not 
// necessarily set when a node is being created.
$op = empty($node->nid) || !empty($node->is_new) ? 'create' : 'update';

Sure, good fix. Thanks!

hi
Just for info after applying the patch, in case error still showing please do :

1- drush rr
2- drush cc all
3(once again) drush cc all
and refresh the page

You may not need to do all this in some environment .

..thanks

When in stable version?

+1 #2, i applied patch on 7.x-1.8 v, thanks, also +1 #22, i have a custom access module and #22 also worked fine.

Is the patch committed to the stable version already?

dercheffe, no -- if I'm interpreting this correctly the current stable release is 7.x-1.8 released 22 September 2016, but the patch wasn't committed until way after that, 8 March 2017.

I would be very appreciative of a new stable release including this patch.

The patch works until I reload the page, then the error returns. I cleared drupal cache and drush cache. I'm on Drupal 7.56, Entity API 1.8.

+1. This really needs to be in a stable release.

This fix is included in Entity 7.x-1.9.