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
That would actually be a nice usability improvement. A lot of people already build search pages with Views, so having an easier way to convert the default search results into a View would make...
[UX] Convert search to a view.
Try using caching in the View settings, set to 24 hours. This should work for anonymous site visitors. I haven't tested this in practice, so this is just a guess.
View to show a different node each day
Have you already played with Views random seed? I belief, what you try to achieve would work with that module. Show only one node and set the sort order to "Global: Random seed" with "...
View to show a different node each day