U4-3251 - Tree syncing doesn't actually sync the current node

Created by Shannon Deminick 28 Oct 2013, 00:59:04 Updated by Per Ploug 01 Nov 2013, 08:38:36

Relates to: U4-3296

Subtask of: U4-2891

For example, if you change the name of a node, the tree sync does not go and refresh that particular node to update it's name. Similarly if you change it's state from published/unpublished/pending version, the tree sync does not update the node to reflect it's new state.

In order to do this, a request needs to be made for the parent node's children, then we filter the child results to find the current node and then replace that node in the tree.

Comments

Shannon Deminick 29 Oct 2013, 21:23:03

Is this fix pushed? Can't see where this fix is made and doesn't seem to be working


Shannon Deminick 30 Oct 2013, 22:36:45

There's still some issue with tree syncing:


Priority: Normal

Type: Bug

State: Fixed

Assignee: Per Ploug

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version: 7.0.0

Sprint:

Story Points:

Cycle: