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
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists