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
Do you have a separate development environment and transfer database and config between sites?
Wierd happenings regarding updates...
This link should work if the VIEW contains a Block and a Page - the link from the block will be directed to this page. I've never used it, so I might be wrong. But what can be done easier is to...
Blog module questions
Thank you very much for your reply! I understood that I first need to create a VIEW. I had assumed that the settings were configured via the block because it’s already included in Backdrop...
Blog module questions