Issue Feature Closed

#99043List Module: Remember sorting per table

Christian Toffolo 11/10/22, 10:45 updated 11/13/26, 18:23

Description

Steps to reproduce:
1. go List module
2. sort table (e.g.: tt_address) by tstamp: records are sorted old first
3. click again to sort by new records first
4. navigate away (e.g.: click another page)
5. already here, table has lost the previously set sorting (tstamp from new to old) and it back to default (very annoying with many records)

Expected behavior:
Sorting per table is remembered by TYPO3

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 3

  1. Georg Ringer commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-13T18:23:59+00:00" > 11/13/26, 18:23 </span>

    Closing as part of a backlog cleanup

    In the Web > List module the sorting is plain request state: sortField and sortRev are only passed via the URL (and carried along by the module’s own links and the shortcut). Nothing is stored in the backend user’s module data, neither per table nor per page.

    Making the sorting sticky would mean introducing a new kind of persisted state and answering questions that have no obvious answer, e.g.:

    • Is it remembered per table or globally? Currently one sortField applies to every table of the view that has such a field.
    • Is it remembered per page (pid) or across all pages? A sorting that “sticks” on a different page can be as surprising as the lost one.
    • How does the user get back to the default (manual) sorting, which is only available when no sorting is active?

    As there is no consistent concept for this and no one has picked it up in years, I’m closing this issue to keep the tracker focused.

    For projects that need it, this can be built in an extension: a backend PSR-15 middleware can store the last sortField/@sortRev@ in the user’s uc (or module data) and add them to the query params of the list module request when none are given. Alternatively, ModifyDatabaseQueryForRecordListingEvent gives access to the QueryBuilder and the record list, which allows persisting and applying a sorting per table.