Uploaded image for project: 'Activation'
  1. Activation
  2. MGNLACTIVATION-66

Activation of subnodes fail when parent node has been renamed but change has not been activated

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 5.0

    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

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              pbaerfuss Philipp Bärfuss
              timopu Timo Pulkkinen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD