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
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists