It just popped into my mind.
Right here: https://api.backdropcms.org/api/backdrop/core%21includes%21cache.inc/fun...
static $cache_objects;
if (!isset($cache_objects[$bin])) {
$class = settings_get('cache_class_' . $bin);
if (!isset($class)) {
$class = settings_get('cache_default_class', 'BackdropDatabaseCache');
}
We are using settings_get function to properly direct cache features based on settings.php
But it is really old way and we have better solution - JSON settings!
So how about to keep this data in config('cache.settings') ?
This way cache settings could be easy transferred between different websites.
Also we can ADD admin/settings/cache page and not experienced users will be able to select different (available) methods for different bins.
Related: #716 #1413
Recent comments
Thanks!! Easiest for me to just give permission for anon users to see the admin theme. That worked. It's just for this one page.
Link field in a Content Type is malformed for annonymous user- Permission issue?
It looks like the screenshot of what you show it should look like is the admin theme whereas what they see is the front end theme. By default, such users won't have permissions to see the...
Link field in a Content Type is malformed for annonymous user- Permission issue?
I've added a new recipe. The recipe has no PHP code. It has two module dependencies (one of those depends on another contrib module and both depend on core modules that are normally enabled)...
The Future of Configuration Recipes for Backdrop CMS