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 for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'
I'll test this tomorrow to see if I can replicate the problem and report back. It's not "per user" so it should be working.
TFA - how to setup fallback options 'per user'
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list