#64764FileList and ElementBrowser must implement a paginate system for files
Description
Hi,
The current system to browse records in a FAL mountpoint doesn’t use offset / limit to display result list. This can be an issue if the folder have a large amount of files, especially in remote mount point.
On our current project, we have implemented a specific driver (using an API) to a document warehouse which have around 1M records with 5 subfolders (and some ‘tags’). The service API implements a paginate browsing system inside queries.
But from now, we can’t use paginate as FileList and ElementBrowser doesn’t use parameters $start and $numberOfItems. These parameters always have zero as value.
Could it be possible to add browsing on results on next major version ?
In addition to a paginate system, a simple search field as on record list could enhance usability in cases with large numbers of records.
Regards,
Clément
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 10
- Feature #23631Pagination on browse link page
- Bug #56746File list always fetches all files in folder
- Feature #64401pagination for elementbrowser
- Feature #66464File selection popup does not use FAL driver count*() methods
- Feature #66608Element browser need some kind of sorting
- Feature #79679File sorting in TBE file selector (configurable)
- Bug #83507Max allowed memory size on FileBrowser.php when trying to implode 36.663 lines
- Feature #83668Make list of files paginatable in file selector popup
- Feature #89709Fileadmin must be more "useable"
- Feature #99517FileBrowser should use paginated views