I’m having a play around in Umbraco 17 (upgraded from 13) and I’ve noticed that there is now paging in the backoffice: if I expand a content node with a few hundred child nodes then it now shows the first 50 followed by a “…” link that I need to click to see the next 50.
I’m struggling to find where to configure this. As I’ll typically need to edit the most recent (and therefore bottommost) node, what used to be one click and a pull of the scroll bar is now click, scroll, click, scroll…
I appreciate that the real solution is to restructure things and not have a huge number of nodes in the same place, but in the meantime, how can I increase the page size or disable paging?
Im not sure if you can change that to be honest. The reason for paging is performance. In Umbraco 13 it could get real slow and I think there was even a limit under water.
What Im curious about is why you wouldn’t configure the parent node as a list view that you can sort by date by default so that the newest node is always at the top?
Yeah this is the use case for list view (now collection view) on the parent doctype. Alternatively you could write a bit of code that on saving the new node, orders the nodes by newest first, but with many nodes this becomes and expensive operation as you’d need to replace the sort order on each node every time (you’re moving let’s say node number 1234 and putting it at sort order 1, so 1 through 1233 need to get a new sort order and each need to be saved to the database).
The original reason is because there were only a couple of dozen nodes in the original design, but then The Users came along
This upgrade is a good opportunity to change things though, since everything needs to go through a full test anyway, so it sounds like that’s the solution. Thanks!
Alternatively you could write a bit of code that on saving the new node, orders the nodes by newest first, but with many nodes this becomes and expensive operation as you’d need to replace the sort order on each node every time
Another option, is to multiply the sort order of a new node by -1. That would be less expensive.
