Problem/Motivation
We have a state get call on every request to check whether we are in maintenance mode, for many sites this might not matter,
but it all sums up.
Proposed resolution
Add an additional flag to settings.php, so you can enable/disable them effectively
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#2 | 2575591-2.patch | 4.18 KB | dawehner |
Comments
Comment #2
dawehnerJust a basic idea so far.
Comment #6
wturrell CreditAttribution: wturrell as a volunteer commentedFWIW I like this idea, although perhaps the documentation in default.settings.php is ambiguous - maybe say:
Comment #7
catchSeems like a good idea to me.
Comment #8
rachel_norfolkI like the idea of not having to do the check every request.
I wonder if it might be even better if the functionality was spun out into a (tiny) core module? That way, it can be enabled in the Standard profile etc but simply disabling the module disables the checking and the UI for maintenance mode.
Would it be possible for a module to do the check that happens currently?
Comment #18
smustgrave CreditAttribution: smustgrave at Mobomo commentedThis issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request as a guide.
Tagging for tests
Tagging for a change record as the service is taking in a new parameter.
Tagging for framework manager too for their thoughts on this change.