[MAGNOLIA-2131] Moving nodes can create inconsistent website-trees on author and public system Created: 09/May/08  Updated: 23/Jan/13  Resolved: 14/Jul/08

Status: Closed
Project: Magnolia
Component/s: activation, admininterface
Affects Version/s: 3.5.4
Fix Version/s: 3.6

Type: Bug Priority: Blocker
Reporter: Wolfgang Habicht Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

http://demoauthor.magnolia.info, http://demopublic.magnolia.info/


Issue Links:
dependency
depends upon MAGNOLIA-1899 activation: if the page (uuid) exist ... Closed
relation
is related to MAGNOLIA-2173 Moving / rename a page on author sho... 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   

Moving nodes can create inconsistent website-trees on author and public system

Can be reproduced by the following:

(on author instance)

  • login as superuser:
  • create the following page structure (website)
    + ...(some other pages, does not matter)
    + page1 (Magnolia Samples: One column page)
    + page2 (Magnolia Samples: One column page)
    + page10 (Magnolia Samples: One column page)
  • activate everything
  • publish everything (in the workflow)
  • create a new user 'emil', set some nice password
  • add the role 'editor' (role, not group, and no other rights)
  • logout
  • login as emil
  • move page1 to page10, click yes to deactivate nodes (tree should now look like the following)
    + ...(some other pages, does not matter)
    + page10
    + page1
    + page2
  • logout

++++++++++++++++++++++++++++++++++++++++++++++++
---> notice that the pages on the demopublic (the public instance) are still the 'old' one:
+ ...(some other pages, does not matter)
+ page1 (Magnolia Samples: One column page)
+ page2 (Magnolia Samples: One column page)
+ page10 (Magnolia Samples: One column page)
++++++++++++++++++++++++++++++++++++++++++++++++

  • login as superuser
  • activate page1
  • publish page1 (in the workflow)
  • activate page2
  • publish page2 (in the workflow)

++++++++++++++++++++++++++++++++++++++++++++++++
---> error-message in workflow (for page2): Can't activate: : Message received from subscriber: Parent not found (not yet activated): page10/page1
---> on demopublic are still the same pages published!
+ ...(some other pages, does not matter)
+ page1 (Magnolia Samples: One column page)
+ page2 (Magnolia Samples: One column page)
+ page10 (Magnolia Samples: One column page)

on demoauthor (author instance) is the 'new' page structure, all 'green' except page2 (-> looks like published)
+ ...(some other pages, does not matter)
+ page10
+ page1
+ page2
++++++++++++++++++++++++++++++++++++++++++++++++

--> page1 and page2 can not be removed on public anymore
--> page1 and page2 can not be published anymore

Suggestion: why not disable moving published pages?
--> de-activate, move, activate is the correct sequence anyway



 Comments   
Comment by Wolfgang Habicht [ 09/May/08 ]

the tree-structures got lost in the original report above, here fixed
+ page10
--+ page1
----+ page2
means page2 is child of page1 is child of page10

-------------------------------------------

  • login as superuser:
  • create the following page structure (website)
    + ...(some other pages, does not matter)
    + page1 (Magnolia Samples: One column page)
    --+ page2 (Magnolia Samples: One column page)
    + page10 (Magnolia Samples: One column page)
  • activate everything
  • publish everything (in the workflow)
  • create a new user 'emil', set some nice password
  • add the role 'editor' (role, not group, and no other rights)
  • logout
  • login as emil
  • move page1 to page10, click yes to deactivate nodes (tree should now look like the following)
    + ...(some other pages, does not matter)
    + page10
    --+ page1
    ----+ page2
  • logout

++++++++++++++++++++++++++++++++++++++++++++++++
---> notice that the pages on the demopublic (the public instance) are still the 'old' one:
+ ...(some other pages, does not matter)
+ page1 (Magnolia Samples: One column page)
--+ page2 (Magnolia Samples: One column page)
+ page10 (Magnolia Samples: One column page)
++++++++++++++++++++++++++++++++++++++++++++++++

  • login as superuser
  • activate page1
  • publish page1 (in the workflow)
  • activate page2
  • publish page2 (in the workflow)

++++++++++++++++++++++++++++++++++++++++++++++++
---> error-message in workflow (for page2): Can't activate: : Message received from subscriber: Parent not found (not yet activated): page10/page1
---> on demopublic are still the same pages published!
+ ...(some other pages, does not matter)
+ page1 (Magnolia Samples: One column page)
--+ page2 (Magnolia Samples: One column page)
+ page10 (Magnolia Samples: One column page)

on demoauthor (author instance) is the 'new' page structure, all 'green' except page2 (-> looks like published)
+ ...(some other pages, does not matter)
+ page10
--+ page1
----+ page2
++++++++++++++++++++++++++++++++++++++++++++++++

--> page1 and page2 can not be removed on public anymore
--> page1 and page2 can not be published anymore

Comment by Jan Haderka [ 14/Jul/08 ]

Fixed as part of proper content move handling MAGNOLIA-1899

Generated at Mon Feb 12 03:33:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.