[MAGNOLIA-2901] Moving nodes in adminCentral shows moved node content as parent node content Created: 15/Oct/09  Updated: 23/Jan/13  Resolved: 09/Nov/09

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 4.1.1
Fix Version/s: 4.1.2

Type: Bug Priority: Critical
Reporter: Christian Ringele Assignee: Jan Haderka
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Browsers I tested on:
Firefox
Safari


Attachments: PNG File MAGNOLIA-2901-after-move.png     PNG File MAGNOLIA-2901-before-move.png    
Issue Links:
duplicate
is duplicated by MAGNOLIA-2904 Moving of pages fails in visualization Closed
relation
is related to MAGNOLIA-2827 The path in AdminTreeMVCHandler is no... 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   

When moving a node in admin central to a different parent node, the tree only shows the content of the moved node (subnodes) instead of the whole tree.

The move occurs properly, and this is "only" a visual issue.

It doesn't seem to be specific to any workspace (reproduced on config, website, dms, ...) nor instance (reproduced on several local ones, demoauthor, ...)



 Comments   
Comment by Christian Ringele [ 15/Oct/09 ]

Phlipp thinks, this issue might be related to the MAGNOLIA-2654.

Comment by Magnolia International [ 15/Oct/09 ]

This issue doesn't seem to happen with 4.1; if someone else could confirm, that would seriously limit the range of possibilities

Comment by Magnolia International [ 15/Oct/09 ]

A quick look through the changes of MAGNOLIA-2654 (Safari 4 compatibility) confirms that these changes were only css-related; I doubt it's related. (although I agree it is one of the changes in 4.1.1 that comes to mind )

Comment by Zdenek Skodik [ 15/Oct/09 ]

didn't occur with 4.1 for me

Comment by Philipp Bärfuss [ 19/Oct/09 ]

just stumbled over that: MAGNOLIA-2827. Might be the change causing this issue here.

Comment by Jan Haderka [ 04/Nov/09 ]

Reverted fix for MAGNOLIA-2827 that was causing the issue and solved the problem in related issue (MGNLDATA-60) differently.
The problem is that once the path is set it will be used during the next initialization of the tree rather then the rootPath (or "/" if rootPath is not set). The code is not really clear on why this is done. See .init() method for details.

Comment by Magnolia International [ 06/Nov/09 ]

What's the status of this issue ?

(the rootPath can be used by tree definitions to only show a subtree)

Comment by Jan Haderka [ 09/Nov/09 ]

Done on trunk as of r29199 and on 4.1 branch as of r29345.

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