Currently, Backdrop makes use of the functions field_defaults_field() and field_defaults_instance() to provide default setting arrays for field and instance. These two functions (not present in Drupal) are hardcoded and the arrays they return cannot be altered in any way, making it impossible to provide custom settings for field info or instance, change the default value for a setting, or add a new settings "key" for a custom settings. It would be pretty straightforward to add an alter hook call before returning these arrays (and ideally we would need to pass additional contextual information to these functions and to the the alter calls). I'm wondering what your thoughts are about doing something like this, and/or if it's contemplated anywhere.
Thanks.
Recent comments
ok I got it the 50M limit is set apparently by backup migrate? the location it is files/private/backup_migrate/manual the thing is I managed to restore but I don't get the contents...
Backup & Migrate path for restore
Hi aubergine. Thanks for posting. These are strange behaviors. For the uploaded files, are you uploading them when you create a new node that has a file field? Or are you uploading...
Files uploaded using add file
I'd like to discuss: Remove the "no space" requirement in "Alternate control statement syntax for templates" of Coding Standards #7231
Weekly Meetings Nov 5th 2026
I'd like to discuss how Backdrop treats default values for node fields. The current behavior when adding and creating content with default values, especially for text-based fields, isn't...
Weekly Meetings Nov 5th 2026
Only if you select "Delete all content in these content types before generating new content."
Devel module deletes default images folder