Description of the need
While working with a new Backdrop project, I really needed to be able to quickly set/change the maintenance_mode using override method from command line or the settings.php file. And since the maintenance_mode variable moved to State database table, I could not use the configuration overrides.
Therefore, knowing that implementation of new features to core would take some time, as a quick temporary solution I've pushed very simple State Override module, which literally consists of 13 lines:
<?php
/**
* Implements hook_boot.
*/
function state_override_boot() {
global $config;
if (!empty($config)) {
foreach ($config['state'] as $key => $value) {
state_set($key, $value);
}
}
}
so now I can simply put lines like:
$config['state']['maintenance_mode'] = TRUE;
$config['state']['cron_key'] = 'w5AXKo9UdkoVRp9rT_0gqtdG2h322LGJ_sYuJN6aWpk1';
to settings.php file and it will work just as desired.
However, I believe it would be really useful for automation purposes and convenience of all future Backdrop developers if core supported overriding State variables.
Proposed solution
Let's get this into core if the consensus says so.
Recent comments
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
If you haven't already, flush all the caches. If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
custom module not showing up in modules list
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
custom module not showing up in modules list