Add paging for IRRE-records (working with many IRRE-entries)
There exist cases when many child-records are added to an entry. If an entry with 50 or more IRRE-relations gets opened in the backend things quickly get slow and are also not really easy to work with. Find a way to handle "many IRRE-relations" in one record.
#1 Updated by Stefan Neufeind over 4 years ago
How could we handle that? As a first step maybe load only the first X records (additional setting in TCA to choose how many?), show how many records there really are and offer a link in the record to load them all? That would at least lower the performance-impact when editing other fields. But to edit even larger amounts of IRRE-records we'd still need proper paging and maybe even searching.
#3 Updated by Felix Nagel over 3 years ago
I've got a use case with five fields, each about 20 IRRE records (Monday-Friday with items). This setup is hardly usable with long loading times (10+ seconds) for opening the record (all items collapsed).
Any hints or tips how to improve loading time? Thinking about splitting into smaller pieces.