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
Oh, thank you! I have also been frustrated with this, but haven't tried since switching from Gin theme.
Problem with Field image • Select existing file
I've found. The problem come with GIN THEME. I test with BASIS, and i can load multiples existing files. To be continued
Problem with Field image • Select existing file
The issue appears to occur when there is an unlimited number of images, or more than one image. That's weird. I'm doing exactly that and never had any problem with images not...
Problem with Field image • Select existing file