![]() |
|
|
|
|
Change By:
|
Andreas Weder
(10/Jul/13 9:18 AM)
|
|
Description:
|
We should prevent users from activating the following nodes in the Configuration app:
* first and second level nodes
* {noformat}/server/filters{noformat} and all subnodes
* {noformat}/server/activation{noformat} 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:
# disable all publish/unpublish actions on any of these nodes
# 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.
We should prevent users from activating first and second level nodes.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
