Description of the need
In https://github.com/backdrop/backdrop-issues/issues/5170 We described how Backdrop allows field configs to exist without a corresponding field data table. A consequence of this situation is also discovered in https://github.com/backdrop/backdrop-issues/issues/3224#issuecomment-903... where if we attempt to save an entity with an attached field and instance, we get an exception.
Proposed solution
This new function would allow Backdrop to check if any storage method described in a field has been set up for that field. Currently in core, we only have field_sql_storage as a method
Alternatives that have been considered
We could also attempt to create storage automatically upon trying to save any attached field, in addition to this check
Recent comments
I don't know if anyone else might wind up here, looking for a way to specify a function in the Field UI which gets called and returns an array for the allowed values... But I made a module...
How to set allowed values in code
Hi Mike This is with the sticky header setting for the table. It looks like perhaps the script that sets the widths is not working quite right though if you set the admin/content view to...
View Title Slightly Skewed
Oh, one more thing. If your date field has a start and an end, then the token is slightly different. [node:field_1st_call_date_time:date:custom:ymd] for the start date, or [node:...
Date token display not using selected format