discuss.answer
-
☆ A M B ☆
- 24,524 Posts
That depends on the server environment. The listing of the resources is done with an AJAX request, and it's probably timing out before processing and returning that many records.
Try installing something like Collections, and converting the parent resource to a Collection container. That way its children are listed in a grid in the parent resource's Children tab upon opening the parent resource for editing, and that grid has paging, so you'll never have all that many resources being listed at one time.
Super! How have I missed that? Just installed, and in 30 sec, have not just solved the problem, but the backend interface is 10x better for that use case.
Thanks so much - will now be adding collections as part of my default set of extras.
Cheers.