Thank you Eugenio for implementing this, I look forward to using this shortly after upgrading to DaDaBik 11.😀

The general idea is the following: from the admin section you can set the maintenance status:

Why you should specify other allowed users other than admins? Here is an example where this feature might be useful: you ("root") are testing a new permissions policy for the group "sales", what should you do?

1) You create a new user "Alice" belonging to "sales" (you only know the password)

2) you put the application in maintenance mode except from users "root" and user "Alice".

3) You access, using two different browsers, the application both as root and Alice so you can set the permissions from one browser and see the effects on the other ones.

4) When you are don, you set the maintenance back to 0

PS: The admin section is never "in maintenance", what you can put in maintenance mode 1 is only the front-end application (index.php)

PPS: For the moment, I wouldn't add any rules about who can change the maintenance mode, basically any admin can change the status of the maintenance mode, even reverting what another admin has done before.

If this gets implemented, it would also be nice to know which user invoked the maintenance mode so if you have many developers, you would know who to ask about when the maintenance will be done and what exactly they are working on, etc. This also begs the question of can one admin user lower the flag set by another admin or will there be a semaphore or locking mechanism of some sort.