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
This backdrop site is how I want to build a multilingual site for a friend's business. Is there a tutorial for how to do this, with the same functionality? I note that the language...
How to translate my site content
Responses: -I can edit nodes -I can access the DB but will need help finding the items - not comfortable poking around. - No errors or warnings in log after visiting pages...
View/Edit tabs missing
Hmm... hard to tell. I don't see any module there that modifies the Backdrop routes for node editing etc. Can you check if you can still edit notes? For example by going to node/NODE_ID/...
View/Edit tabs missing
Thanks a lot for the help, solved it.
How to Restrict User Access to Site-Wide Images in the Form Editor
Don't worry. Another way to help out is by testing fixes that others provide and clearly documenting and new issues you find in the issue queues. Sometimes that can be the thing that allows it...
managing draft revisions while still having a version published