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
I've moved this to How To and Troubleshooting as more people will see it here. I've also put the code in a PHP code block to make it more readable.
Filter view on date
@xorgev Thanks for linking to this video. It is a good one that I had not seen before. There are lots of resources on the Internet for Backdrop CMS and it is challenging to figure out how they...
Suggestion to improve the visibility of helpful content for new users
This is helpful. When I Googled for suggestions about the error message, I found an old entry in Stack Overflow that suggested increasing max_connections. I passed that along to the hosting...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?