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
It's great that everyone has a choice. I'm currently making a website where the H1 title is located at the top of the page in full width with a background image, 50vh height, how do you like...
Block title combo and 2/3 things
In the end, I use my <h1> with my custom layout just before the region for the content and i make a preprocess_theme for site_identity. <?php print theme('site_identity'); ?>...
Block title combo and 2/3 things
Choosing to not use the "Page title combo" block on content can also be helpful if you want to arrange the "Page tabs" menu and "Page title" differently.
Block title combo and 2/3 things