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
So the implication is that another module is causing the trouble. Now for the slow process of elimination... Sounds plausible. And good luck with digging...
How to troubleshoot interactive image cropping modules?
I’ve just set up a clean install in MAMP and Focal Point works fine. *sighs So the implication is that another module is causing the trouble. Now for the slow process of elimination...
How to troubleshoot interactive image cropping modules?
Here’s the edit screen with the Focal Point instructions below: If I click on the Preview link, I get this: And no errors in the console.
How to troubleshoot interactive image cropping modules?