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
Tried and successfully applied DrAlbany's method with the form https://www.drupal.org/sandbox/grobot/2105379stickman hook. I also encountered the same situation. Thanks DrAlbany
Ubercart - Auto increment SKU
Since before migration you need to prepare the Drupal site - disabling and removing all modules, disabling themes, as part of the preparation you can clear the cache and logs, delete the search...
Trimming the size of my database for D2B_migrate not to error out (Request Entity Too Large / 504 Gateway Time-out)
QuickTabs is now available!!! But does not work as expected, already reported (https://github.com/backdrop-contrib/quicktabs/issues/14). Maybe an alternative solution using Views...
Quick Tabs (or method to simulate)