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
This link should work if the VIEW contains a Block and a Page - the link from the block will be directed to this page. I've never used it, so I might be wrong. But what can be done easier is to...
Blog module questions
Thank you very much for your reply! I understood that I first need to create a VIEW. I had assumed that the settings were configured via the block because it’s already included in Backdrop...
Blog module questions
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module...
Weekly Meetings July 23rd 2026