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
RE: duplicate files —If an image is disassociated from any content, the system will delete it after x number of hours. (Six, I believe.)
Problem with Field image • Select existing file
For now, I’ve switched to the Seven theme. It’s a very good theme, too. Finally, "select existing file" is important. Otherwise, you end up loading tons of unnecessary, duplicate...
Problem with Field image • Select existing file
Oh, thank you! I have also been frustrated with this, but haven't tried since switching from Gin theme.
Problem with Field image • Select existing file