We have a major client running v4.0.3 of Umbraco. As it's such a big client we haven't upgraded the umbraco version yet.
In the content section, we have a global-node, containing around 1060 nodes. This all works fine, but if we want to sort the nodes the back office kind of stops working.
To be more precise, we're clicking the "Sort"-option on the global node, and then we want to sort the nodes alphabetically. So, we're clicking the Name-column header and the nodes are sorted quickly in the popup-window. But when we're hitting the OK-button and the loading-bar-popup shows up, the sorting will never end. This means that when we're doing this, the loading-bar just keeps going and going and the sorting is never ended.
My question is: Could this be a gub or have we hit a performance top doing this operation i 4.0.3? I know that the back office has been speeded up a lot in the never versions, but I could be great to know if anyone have got some facts on this excact issue in 4.0.3
I have no facts/stats about the content tree in v4.0.3 ... but I do know that the JavaScript for the trees was rewritten in v4.5 and resolved a LOT of issues.
Some of the projects I worked on using v4.0.3 did hit various problems when the content tree got quite large, e.g. over 1000 nodes.
Difficult to recommend a solution.... possibly move nodes into manageable subfolders? or if possible ... *dun*dun*dun* upgrade to v4.7?
Actually we have begun the "subfolder"-solution creating a folder for each letter, but still it could be interesting to know if this was a bug or we just hit the performance top :)
Possible sortingbug in 4.0.3
We have a major client running v4.0.3 of Umbraco. As it's such a big client we haven't upgraded the umbraco version yet.
In the content section, we have a global-node, containing around 1060 nodes. This all works fine, but if we want to sort the nodes the back office kind of stops working.
To be more precise, we're clicking the "Sort"-option on the global node, and then we want to sort the nodes alphabetically. So, we're clicking the Name-column header and the nodes are sorted quickly in the popup-window. But when we're hitting the OK-button and the loading-bar-popup shows up, the sorting will never end. This means that when we're doing this, the loading-bar just keeps going and going and the sorting is never ended.
My question is: Could this be a gub or have we hit a performance top doing this operation i 4.0.3? I know that the back office has been speeded up a lot in the never versions, but I could be great to know if anyone have got some facts on this excact issue in 4.0.3
Thanks :)
/Kim A
Hi Kim,
I have no facts/stats about the content tree in v4.0.3 ... but I do know that the JavaScript for the trees was rewritten in v4.5 and resolved a LOT of issues.
Some of the projects I worked on using v4.0.3 did hit various problems when the content tree got quite large, e.g. over 1000 nodes.
Difficult to recommend a solution.... possibly move nodes into manageable subfolders? or if possible ... *dun*dun*dun* upgrade to v4.7?
Cheers, Lee.
Hi Lee, thanks for your answer.
Actually we have begun the "subfolder"-solution creating a folder for each letter, but still it could be interesting to know if this was a bug or we just hit the performance top :)
/Kim A
is working on a reply...