Description of the need
Running the brush cget *maintenance* command gives:
docker@cli:/var/www/docroot$ brush cget *maintenance*
System core settings (system.core.json)
+------------------------------+-----------------------------------------------------------------------------------------------------+
| Configuration key | Value |
+------------------------------+-----------------------------------------------------------------------------------------------------+
| maintenance_mode_message | [site:name] is currently under maintenance. We should be back shortly. Thank you for your patience. |
| maintenance_page_maximum_age | 10 |
| maintenance_theme | |
+------------------------------+-----------------------------------------------------------------------------------------------------+
which means the three keys found above reside in the system.core.json file as a configuration setting, while at the same time the maintenance_mode has been converted to a state setting and is stored in database.
This kind of separation of related settings creates dis-ambiguity for developers as they need to deal with two different storage types working with close related settings.
Proposed solution
Would be nice to either move all maintenance-related settings to State or maintenance_mode to Config and keep them together.
Recent comments
Hi Jim..., I did something similar for a new site ive created parallax-news.com where the poster can add an image and a blue background with text shadows to make text more readable...
How to access node fields in block template files
Thanks people. I went ahead and created a View block using the BG image formatter. I might still end up messing with template files because I’ll probably need to overlay a graduated...
How to access node fields in block template files
Hi Coffee70, How can I determine what is causing this warning and what exactly needs to be done to resolve it, other than uninstalling Honeypot completely? It doesn't...
Warnings after installing Simplenews 1.x-1.2.3