[MGNLUI-1507] CLONE - Disable activation in the config tree for some nodes to prevent trashing the public instance Created: 31/May/13  Updated: 10/Mar/21  Resolved: 10/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.0.1
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Jaroslav Simak Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MAGNOLIA-5057 Disable activation options in Configu... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

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.



 Comments   
Comment by Jan Haderka [ 10/Jul/13 ]

apart from 1st and 2nd level, following nodes (and their subnodes) should be banned from activation including all their subnodes:

  • /server/filters
  • /server/activation

Andreas: thanks, integrated this comment into the description above.

Comment by Roman Kovařík [ 10/Mar/21 ]

Closing as doesn't seems to be critical anymore and we are moving away from JCR config in general.

Generated at Mon Feb 12 08:47:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.