The argument order in module_load_incude is frustratingly stupid.
module_load_include('inc', 'node', 'node.admin');
It requires devs (even those of us who use this thing all the time) to continue to look up the order because it's so non-intuitive. Ideally, this function would not be specific to modules, and would allow you to specify the entire file name as a single argument. something like...
backdrop_load_include('module', 'node.admin.inc');
or
backdrop_include_file('theme', 'basis', 'template.php');
We could even go one step further and always limit the search for .tpl.php files to the modulename/templates or themename/templates directory, .css files to modulename/css or themename/css and .js files to modulename/js or themename/js. This pattern can be extended to anything else we decide to neatly place into subdirectories (.test files in modulename/tests, etc).
This issue will depend on the addition of the BC layer, and the dupal.inc file.
Recent comments
Hmmm, from D7 ancient tomes: from https://drupal.stackexchange.com/questions/7056/limit-which-roles-can-view-a-node-basing-on-its-content-type yet https://docs.backdropcms.org/api/...
node access
I also note on this screen: "Furthermore note that content which is not published is treated in a different way by Backdrop: it can be viewed only by its author or users with the...
node access
I am seeing via dpm debug that the nodes that are authored by someone else are not even being interrogated at the view level; they are simply avoiding the hook_node_access call. Yet the...
node access