mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-07-11 22:13:49 +02:00
6c96c490c6
This edge case can occur when a large tree is cached in HTML already, without any nodes expanded via ajax. If a new node is added with a parent that's not existant, it was simply placed on the root node. This is a display bug, a full CMS refresh fixes it. Fixes a related bug where tree causes (view) duplicates, where the same node is rendered twice. This was due to the whole subtree being refreshed (including the new node) through jstree's built-in "open"/"select" events, while at the same time creating a new node through updateNodesFromServer() callbacks. Also added a global tree loading indication to make it clear that the tree is still processing. See https://github.com/silverstripe/silverstripe-cms/issues/872 |
||
|---|---|---|
| .. | ||
| themes | ||
| _actionTabs.scss | ||
| _forms.scss | ||
| _ieShared.scss | ||
| _menu.scss | ||
| _mixins.scss | ||
| _ModelAdmin.scss | ||
| _preview.scss | ||
| _SecurityAdmin.scss | ||
| _sprites.scss | ||
| _style.scss | ||
| _tree.scss | ||
| _typography.scss | ||
| _uitheme.scss | ||
| editor.scss | ||
| ie7.scss | ||
| ie8.scss | ||
| screen.scss | ||