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
Thank you, this is a very useful workaround for preparing a clean import list. One concern remains, however: if Simplenews 1.x-1.2.3 still treats blocked user accounts as invalid...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
@Amilenkov, I have an idea for your use case where you want to avoid re-subscribing people who have explicitly opted out: Build a view of simplenews subscriptions, and filter by Status (...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
"modules to help someone monetise their own website"
How to monetize a Backdrop site