You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I am a huge fan of your module, cleans up our sitetrees very nicely, thank you for sharing!
I discovered a bug with nested sitetree items. The case I had was a root-level item, with subitems, and subsubitems. Whenever the root-level item was expanded (by clicking the little arrow and /admin/pages/getsubtree?ID=...&ajax=1 was called), the interface moved all subitem and subsubitems up one level in the interface. They weren't actually reparented (the database still showed them to be subitems of the correct parent), but the tree moved them up. I traced the origin of the bug back to a closing that apparently is not needed. So my solution was to change the LeftAndMain_TreeNode.ss to the following (basically I just removed the at the end ;-) ):
This is in line with /framework/admin/template/Includes/LeftAndMain_TreeNode.ss (which also has no ending ). Could you incorporate this fix with the next version?
The text was updated successfully, but these errors were encountered:
Hi! I am a huge fan of your module, cleans up our sitetrees very nicely, thank you for sharing!
I discovered a bug with nested sitetree items. The case I had was a root-level item, with subitems, and subsubitems. Whenever the root-level item was expanded (by clicking the little arrow and /admin/pages/getsubtree?ID=...&ajax=1 was called), the interface moved all subitem and subsubitems up one level in the interface. They weren't actually reparented (the database still showed them to be subitems of the correct parent), but the tree moved them up. I traced the origin of the bug back to a closing that apparently is not needed. So my solution was to change the LeftAndMain_TreeNode.ss to the following (basically I just removed the at the end ;-) ):
This is in line with /framework/admin/template/Includes/LeftAndMain_TreeNode.ss (which also has no ending ). Could you incorporate this fix with the next version?
The text was updated successfully, but these errors were encountered: