We should prevent users from activating the following nodes in the config tree:

• first and second level nodes
• /server/filters and all subnodes
• /server/activation and all subnodes

Activating any of these nodes might trash the public instance and seems to have caused about 10% of all support requests in the past.

In 4.5, AdminCentral eventually prevented such activations. For 5.0, we should add such checks again. Possible options are:

1. disable all publish/unpublish actions on any of these nodes
2. leave the actions enabled, but show a warning message explaining that the activation can't be done and why.

In order to avoid too many support requests, we should aim at a solution similar to the second option. The reason why such an activation is not allowed is not very intuitive to non-savvy users, so simply disabling actions might cause confusion.

Example on how this causes a failure:
Activate whole modules folder on author ->
Public instance then redirects to /.installer but cannot even perform installation, because the nodes already exist.