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.
Recent comments
Welcome to the Backdrop CMS community! For me, Backdrop CMS came to deliver exactly what I had wished for in Drupal 7 — especially its low resource consumption and its ability to run on...
BFT Tool v1.8 by BossV For All Android Devices Latest (2027)
Here's a fun hack: You can remove any css file in a custom theme by defining a file with the same name in the theme's info file, but not actually having a file with that name in the theme...
How to get rid of grid-flexbox.css
What is demoralizing for the maintaineers when someone mentions the flaw of a useless buggy feature? A different opinion should always be a motivation not otherwise. I will mark this one...
Files uploaded using add file