[MGNLACTIVATION-66] Activation of subnodes fail when parent node has been renamed but change has not been activated Created: 14/Oct/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Timo Pulkkinen Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: parentnotfound
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

Didn't find this reported earlier, so here comes:

Steps to reproduce:

1. Create a simple hierarchy of pages, e.g.:
/parent/
/parent/child1
/parent/child2

2. Activate all nodes
3. Rename node parent to something else, e.g. parent2
=> After this parent2 is indicated to be changed after last activation (but not deactivated)
=> Statuses of children are unchanged and appear to be public

4. Try to activate some of the child nodes, e.g. 'child1'
=> At least in version 4.1.1 activation fails with parent not found exception message

The problem is resolved if the parent node is re-activated but this operation apparently is not intuitive to the user and causes confusion.

Possible fixes:

  • Preferably make node to be reactivated automatically after renaming if node is already active
    -Pros: Prevents deactivating by accidental renaming impossible
    or:
  • Deactivate whole subhierarchy if parent is renamed
    -Cons: Accidental renames may cause large number of content to disappear temporarily from public site


 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Sun Feb 11 22:59:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.