Description of the need
I've gotten bitten a few times when file ownership or permissions gets set incorrectly on config/active
such that the active configuration directory isn't writable. Since some modules still incorrectly store states in config instead of in the states storage system, that can lead to surprisingly broken sites with entire pages failing to load and displaying "Failed to write configuration file" errors.
Proposed solution
I suggest adding a check to make sure that the active configuration directory is writable to the system requirements function. That would display an alert on the Backdrop status page and could easily be detected by monitoring systems.
Alternatives that have been considered
I'm going to work on adding this check to our sites via a custom module, but this seems like an issue universal enough to merit addition to core.
Recent comments
Does backdrop have a super admin that's different than users assigned the administrator role? Sort of. Backdrop has an administer role that can be granted specific...
content_access_node_access_rebuild doesn't exist
@GOA_TrishaLynn - Thanks for your comments. Are you having any trouble finding the documentation you are looking for?
What are (should be) the prerequisite skills to install and configure a site with Backdrop CMS?
No, both those .json files are extant in the files/config_XXXXX/active folder. Views UI wasn't enabled. I did so, and now I can manage content and people. Thanks!
content_access_node_access_rebuild doesn't exist