node_load() should be the preferred method to create a node object for an existing node. It allows third-party module to change the node data, or to load the data the third-party module adds to the nodes.

Comments

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Postponed

This will not happen for the 1.0 release.

Anonymous’s picture

Anonymous (not verified) commented

Don't we just want to know if the node exists and is accessible by the anonymous user? What benefit is it to have all of the node object when we don't use the node data itself?

dave reid’s picture

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

Other modules may use data from the node object parameter in node_access(). Not using node_load is just an invitation for something to go wrong or fringe cases that are hard to track down later.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Don't we just want to know if the node exists and is accessible by the anonymous user?

Even in the case you are just verifying if the node is accessible from the anonymous user, a module could need some extra fields to decide if the node is accessible.

Anonymous’s picture

Anonymous (not verified) commented
Status: Postponed » Active
dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (won't fix)

At this point, this issue is going to be marked as won't fix. This is out of the project branch scope.