Now that we have fixed the usage of authorize.php when using Installer module for manual module installs (#1920), it's become clear that we should be using authorize.php for all downloading/installing of modules/themes/layouts.
Without using authorize.php, Installer module only works if the owner of web root directory and the web server user are the same. By using authorize.php, we could enable users to more securely set up their site and still allow modules to be downloaded/installed. If the owner of the web root is the web server user (as is the case in most shared hosting environments and Pantheon), then we don't have a problem. But when these users are different, authorize.php could enable the use of the Installer UI.
GitHub Issue #:
2271
Recent comments
If choosing the Views approach you can also use https://backdropcms.org/project/eva which allows you to place the list with more flexibility.
Backlinks for Entity Reference?
Thanks. It still took a lot of trial and error for all the settings within the settings, but I eventually got it to display based on these instructions.
Backlinks for Entity Reference?
Another easy way to do this is to use the module Corresponding Entity References (cer). You would need to add an entity reference field in the authors content type pointing at the book, then set...
Backlinks for Entity Reference?