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
Hi Jochen You could test https://github.com/backdrop-contrib/commerce_invoice_receipt which doesn't yet have a release, but may meet your needs when combined with other modules to generate...
Commerce modules
Setting up a multisite with multilingual support can definitely get a bit tricky with all those configurations. If you're looking for a way to keep things clean, I've found that using a quick...
Multisite for multilingual website
Start with basics: install modules for meta tags and XML sitemaps, set proper alt text on images, and keep URLs clean. Backdrop SEO is mostly about structure and content quality, not tricks.
How to Improve SEO Performance in Backdrop CMS