Issue Feature New

#94617Introduce generic record preview / listing

Oliver Hader 07/22/21, 13:29 updated 11/09/26, 11:29

Description

Ideas by Benni Mack:

TYPO3 Backend uses various places where records are shown, in different ways. There are lots of issues with the rendering, as it is completely re-built on most places of TYPO3 Backend.

Some current places:

  1. Content Elements in Page Module
    • There is a standard renderer, and a possibility to also use custom renderers
    • Everybody needs to built their own renderer to e.g. resolve connected File References
    • Somehow it allows to link to the FormEngine, but only if the user has access to
  2. Record Listing
    • As known from the List module, this enables to show a record with flexible column view, but is not useful for e.g. tt_content because it does not respect the CType and relevant fields for each type. Same goes for pages and fields like “shortcut_mode” or “url” which are only relevant for a specific type
  3. Element Browser
    • The list is also used in a limited rendering in the Element Browser, but for e.g. tt_content records, it shows the infamous “[no title]” when dealing with e.g. plugins. It is not possible to modify the listing properly, especially for specific types.
  4. Workspaces Module
    • The list module shows sub-records (e.g. Inline Element), which DB list does not show, but at the same is not configurable at all.
  5. BE Users / Redirects
    • A custom listing is added, where functionality like listing / grouping needs to be re-implemented over and over again.
  6. Files
    • The DB list is sometimes used, but on the Filelist module it is not always in use.

This approach aims to unify the different renderings in various ways, allowing to standardize the output while starting to use Web Components / Custom Elements, which could / should be re-defined on a per-record and per-record-subtype basis.

Registration:

$GLOBALS['TCA']['tt_content']['types']['textpic']['display'] = [
    'small' => ['header'],
    'medium' => ['header', 'bodytext', 'asset']
    'large' => ['header', 'bodytext', 'asset'],
    'full' => ?
    'renderer' => MyRenderer::class
];

class RecordDisplayInterface {
    public function resolveColumns(string $table, array $row, string $displayMode): array
    // @todo: deal with JS includes
    public function render(string $table, array $row, string $displayMode): string
}

Display Modes:

  • small
  • medium
  • large
  • list

Actions:

  • select checkbox (Multiselection)
  • delete/hide
  • link to edit

Reviews 1

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch

Commit message
[FEATURE] Introduce generic record preview / listing Resolves: #94617 Releases: main

History 24

  1. Gerrit Code Review pushed patch set 2 for master to change 68499 status New Under Review <span data-processor="relativetime" data-value="2021-07-22T13:58:55+00:00" > 07/22/21, 13:58 </span>