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
Hi I added the 2 additional settings in settings.php, did a restart - and the error disappeared! Thanks for the support! (but the issues with the conversion still remain .....
Problem with utf8mb4 Format when importing database
With JQuery, simple and fast. Or put all possible links in one menu, and hide unnecessary with CSS mediaquery.
Different primary menus depending on the viewport size?
I wonder if what is happening here is the default database settings are for utf8mb4 if the database server supports it. In settings.php or settings.local.php if that's where you put your...
Problem with utf8mb4 Format when importing database
I've not done this with a menu before but something similar with different Views presentation blocks for different resolutions (i.e. not just responsive but a different presentation method...
Different primary menus depending on the viewport size?
Thank you for all your help. In the meantime I just edited the export db-file and removed the top line with the sandbox comment. --> Still the same issue. I exported also with the...
Problem with utf8mb4 Format when importing database