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
I don't know if anyone else might wind up here, looking for a way to specify a function in the Field UI which gets called and returns an array for the allowed values... But I made a module...
How to set allowed values in code
Hi Mike This is with the sticky header setting for the table. It looks like perhaps the script that sets the widths is not working quite right though if you set the admin/content view to...
View Title Slightly Skewed
Oh, one more thing. If your date field has a start and an end, then the token is slightly different. [node:field_1st_call_date_time:date:custom:ymd] for the start date, or [node:...
Date token display not using selected format