Feature #9063


Improve editing of multiple records

Added by Dmitry Dulepov almost 14 years ago. Updated over 2 years ago.

Could have
Backend User Interface
Start date:
Due date:
% Done:


Estimated time:
PHP Version:
Sprint Focus:


Currently multiple records are shown one after another. If there are many records, this is inconvenient because:
- causes too much vertical scrolling
- with complex record forms it is hard to distinguish between records

There can be two solutions.

1. Put them into tabs.
This is not perfect because tabs inside tab is a bad idea. Also there can be flexforms with tabs inside regular forms, which will create even more nested tabs.

2. Make something similar to IRRE collapsing.
This would open close individual forms. Ideally there should be a docheader buttons to expand/collapse or "jump to" a specific record (simple drop down ExtJS menu).


Screen_Shot_2013-08-09_at_11.12.29.png (242 KB) Screen_Shot_2013-08-09_at_11.12.29.png Benjamin no-lastname-given, 2013-08-09 11:15

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #53941: UX: Multi-edit records looks uglyClosed2013-11-25

Actions #1

Updated by Steffen Gebert almost 14 years ago

I use this feature to not need many clicks, but only scroll downwards.

Actions #2

Updated by Steffen Kamper almost 14 years ago

It also depends on usage. I use that feature in list view very often, eg to set a page property for all subpages. Then i scroll down and edit nearly every record one after the other. Very useful, and any collapse would disturb this way of quick edit.

For the distinguishing - i would prefer alternated bg colors like in a grid instead of tabs or collapse. While you're edit you won't use the mouse, so cool would be:
TAB to jump to next form field
CTRL+TAB to jump to next record form field

Actions #3

Updated by Lars Zimmermann over 13 years ago

  • Status changed from New to Needs Feedback

Can we close this issue? It seems there's no real discussion here?
What about Steffens idea of being able to browse the page via keyboard? But this is more a technial and not an HCI issue?

Actions #4

Updated by Wegner over 13 years ago

For real improvement of usability I suggest an additional solution 3. It's not about layout but funtionality. So I'm not sure if this is the right place for posting or if I should better create a new issue.

Imagine you have to insert the same data into 20 manually chosen records. Why would you want to scroll, click and edit all the 20 records? This is highly inefficiently.

=> It should be possible to edit all the 20 records at once.
=> You should be able to decide wether you want to overwrite all existing data with the new value, delete data or to add new values.

E.g.: You create a new tt_news category 'dogs'. There are already 43 articles regarding dogs. After manually hooking these articles you just click something like 'edit all at once [add values]' and chose tt_news cat 'dogs'. Done. Spend your working time on more difficult tasks.

The old way is only reasonably if you have to insert different data into each record.

For me it's like what Steffen Gebert wrote: I'd prefer to not need many clicks.

Actions #5

Updated by Jens Hoffmann over 13 years ago

  • Category set to Interface

Seems like there is an Issue - but no solution :)

  • Alternating BG color is a no brainer and be in there.
  • A Form field at the top should be there to .. to manipulate all data at once (Modify, Delete).
  • Tabs are a no go here .. and collapse isn't a good solution, too.
    We got a Hardware Interface (Scroll wheel) and we should use that instead!
  • A live list could be a solution to improve the performance (But that not real HCI Issue than)

Any other suggestions?

Actions #6

Updated by Benjamin no-lastname-given almost 11 years ago

I would like to mass-edit records from a different language.
But there is no language dropdown at the top on the edit page and in the list view i can only select the records with default language.

Actions #7

Updated by Benni Mack over 7 years ago

  • Tracker changed from Suggestion to Bug
  • Project changed from 78 to TYPO3 Core
  • Category changed from Interface to Backend User Interface
  • TYPO3 Version set to 8
Actions #8

Updated by Alexander Opitz over 7 years ago

  • Tracker changed from Bug to Feature
  • Status changed from Needs Feedback to New
  • Target version set to 9 LTS
Actions #9

Updated by Riccardo De Contardi about 7 years ago

Actions #10

Updated by Susanne Moog almost 6 years ago

  • Target version changed from 9 LTS to Candidate for Major Version
Actions #11

Updated by Christian Kuhn over 2 years ago

  • Status changed from New to Rejected

Hey. I'm going to set this ancient issue to 'rejected' for now: There is still no good idea on how to improve the situation and the issue does not seem to be so pressing that anyone is willing to work on it for years. I guess if we tackle this one way or the other, it will happen in a fresh issue anyway.


Also available in: Atom PDF