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
I'd like to learn more about options to handle payments in Backdrop: Ubercart and Commerce vs. standalone solutions and integrations with modules like Webform or Registration...
Backdrop Live November 2025
The accepted answer refers to Drupal and has weird formatting (missing capitalization at the beginning of paragraphs). Seems to me it was either copied from a Drupal post, or AI generated...
Ckeditor 5 click to activate
For the Dev meeting: I would like to discuss whether we should have a policy in the Forum that AI provided solutions should be attributed to AI and which model it is from. We have started...
October 16th 2025 Weekly Meetings
Sudipto, you may have more luck in the CiviCRM forums for this as this looks like a CiviCRM error. Many people use Stripe in Backdrop without issue, albeit it can take a bit to get setup.
Getting Error after submitting event register form By using Stripe Payment Processor
Yes, that would be too much 'hacking' for me. I will stick with 'multiple values'
Expanding a field