Description of the need I have adopted a practice of moving config files from the files directory to a special config directory 1 level below Backdrop CMS root. However, this is not consistent across all my sites. I think it would be great if the status report page showed where Backdrop CMS is actually looking for the config files (as set in the settings.php file)
Proposed solution Add "config directory" path to the status report.
Alternatives that have been considered None
Additional information This seems pretty obvious to me so I expect that there is another ticket somewhere discussing this that I was unable to find.
I am also considering that this MIGHT not be a good idea for security reasons. Maybe there are good reasons to not include the path to these files in the UI. I'm not sure if this would be a problem and look forward to hearing from others.
Recent comments
Thanks. I think, for me, the user-interface issue is that one uses (can only use) the "big" configure to add a first condition. And that made me think that I should use that same method to add...
Blocks (custom) not displaying in Harris sidebars with visibility condition set to more than one url path (node)
Just wanted to add-- anyone trying to set these permissions while running from Synology web station (DSM 7x) like I am, the apache user is apparently "http". So use: chown -R http....
can't install modules: "Error installing Devel. Permissions are not set up properly."
Correct, if you add multiple condition statements they are treated as AND so it would appear to the system as: node/103 AND node/91 which will never happen. Glad you found the way to...
Blocks (custom) not displaying in Harris sidebars with visibility condition set to more than one url path (node)