Project

General

Profile

Actions

Feature #65505

open

Add paging for IRRE-records (working with many IRRE-entries)

Added by Stefan Neufeind over 9 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2015-03-04
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
medium
Sprint Focus:

Description

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.


Related issues 4 (2 open2 closed)

Related to TYPO3 Core - Feature #17247: Load Inline Elements On DemandClosedSusanne Moog2007-04-26

Actions
Related to TYPO3 Core - Bug #82100: Backend Form Dataprovider load every foreign Entity, not only the related oneUnder Review2017-08-14

Actions
Related to TYPO3 Core - Feature #56490: FormEngine IRRE limitClosed2014-03-03

Actions
Related to TYPO3 Core - Task #100109: Superfluous access permission checks in InlineRecordContainer and FileReferenceContainerUnder Review2023-03-07

Actions
Actions #1

Updated by Stefan Neufeind over 9 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.

Actions #2

Updated by Georg Ringer over 9 years ago

I can't imagine where I need more relations. I am not sure if the Cms needs to cover this edge case...

Actions #3

Updated by Felix Nagel over 8 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.

Actions #4

Updated by Tymoteusz Motylewski over 6 years ago

Actions #5

Updated by Tymoteusz Motylewski over 6 years ago

  • Related to Bug #82100: Backend Form Dataprovider load every foreign Entity, not only the related one added
Actions #6

Updated by Tymoteusz Motylewski over 6 years ago

Actions #7

Updated by JAKOTA Design Group GmbH almost 2 years ago

I'm interested in this too.

We have a setup where the IRRE records has about 900 entries. The backend is unusable with those records enabled.

Luckily for us I can just hide them as those are not needed all the time.
But having a pagination for IRRE records would make things easier.

Thanks

Actions #8

Updated by Christian Eßl over 1 year ago

  • Related to Task #100109: Superfluous access permission checks in InlineRecordContainer and FileReferenceContainer added
Actions

Also available in: Atom PDF