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
Welcome to the Backdrop CMS community! For me, Backdrop CMS came to deliver exactly what I had wished for in Drupal 7 — especially its low resource consumption and its ability to run on...
What Makes a Good CMS Experience for Website Owners and Developers?
Here's a fun hack: You can remove any css file in a custom theme by defining a file with the same name in the theme's info file, but not actually having a file with that name in the theme...
How to get rid of grid-flexbox.css
What is demoralizing for the maintaineers when someone mentions the flaw of a useless buggy feature? A different opinion should always be a motivation not otherwise. I will mark this one...
Files uploaded using add file