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
Thanks guys, that worked. Although I did get this output: Notice: unserialize(): Error at offset 0 of 91 bytes in content_access_update_1002() (line 134 of /home/crm/domains/...
Drupal 7 Migration, content_access issue
Hello FTW, Did you ever resolve this challenge?
RSS Help Needed
Thanks!
Webform - can they be saved?