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
One effective way to handle this in Backdrop CMS without adding heavy modules is to use a simple "File" field on your content type and set the display formatter to "Generic file." This creates a...
Simple PDF Upload & Link
That sounds like a frustrating loop. Since you're considering a manual update, overwriting the /core folder is usually the most reliable way to get past those archive errors. Just make sure to...
Update Problems
I’ve been looking into different ways to handle integrations more efficiently, and the approach you mentioned here clarifies a few things I was stuck on. Definitely going to try implementing...
Integration
It’s really interesting that clearing out the menu_links table and reinstalling the Admin Bar module did the trick. Menu corruption is such a common headache when moving from D7 to Backdrop,...
Upgrading from Drupal 7 - problem
Restore Newsletter Subscriptions from a Dev Website In my last comment, I described a way to restore newsletter subscriptions from a database backup. The method involved directly editing...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled