Currently, anytime a module adds a new configuration default, the module maintainer needs to write a hook_update_N() to merge the new default into the active set. This violates DRY by putting the default in two different places, and should not be necessary for all the same reasons hook_install() doesn't need to call schema_install().
Backdrop's update process can detect changes to the default sets and apply the changes automatically.
Recent comments
@themetman Good to hear your solution. May be helpful for others in the future.
Write Permission Problems on files, ../private and /tmp on my Laptop
It was the ProtectHome setting in the apache service which was the problem. I did this: systemctl edit apache2.service Then added this: [Service] ProtectHome=no...
Write Permission Problems on files, ../private and /tmp on my Laptop
I don't have leaflet, but I have experienced random disappearances of the bar over the years. I quit spending time on it, but not before adjusting the css spacing, which did reduce the number of...
Disappearing administration bar. Is this a Leaflet or a Backdrop bug?