With help from others in the Backdrop zulip chat, the private file path can be configured in the settings.php or settings.local.php using either relative or absolute paths. To do this, add the following line:
$config['system.core']['file_private_path'] = '../files_private';
The private file path will show in the GUI at admin/config/media/file-system
and it leaves the default download method as public, however modules that require private files such as backup_migrate and the demo module for snapshots will use the path. The default download method can be changed to private as needed.
Subsequently, changing the private file path in the GUI will likely not work as it will be overridden by the settings.php or settings.local.php configuration. Nonetheless, there are cases where this approach may be useful.
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface
I'm not sure if this is helpful, but here are pages in Backdrop documentaion about server level permissions. https://docs.backdropcms.org/documentation/file-permissions-and-ownership...
Update Core and Theme via Web interface
Just ran into this issue while upgrading modules on a site I'm setting up. I'm confused. Does this mean that /modules needs to be owned by www-data? (Not just that www-data...
Update Core and Theme via Web interface