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.
GitHub Issue #:
1832
Recent comments
OK, I did some more testing and figured this one out. In the paragraphs field setting for each content type you are using them, you can make the following selection for Default Edit Mode. I was in...
How to use 'Paragraphs Editor Preview'
Typically in a basic site, and as far as I know (I may be wrong) Backdrop doesn't store cookies for anonymous users, EXCEPT if you have things that need to persist, for example, if you create a View...
Does Backdrop set any Cookies / session variables for guests?
A couple of other things to keep in mind: - Roles in Backdrop do not use numeric IDs, but machine names. I see that the database insert command is trying to insert a numeric id as a role - Is this a...
Importing users from D7 site using Feeds - uses insert rather than update