Feature #17225
closed
Pagination to the List module
Added by Dmitry Pikhno over 17 years ago.
Updated over 14 years ago.
Description
here is the diff that creates same functionality as list_adv extension.
http://typo3.org/extensions/repository/view/list_adv/1.1.2/
user is able to switch view from default fwd/rwd buttons to pagination by adding to PageTS: mod.web_list.pagination = 1
Also added following tweak: after editing and closing some record the List view stays on same page where you clicked "edit".
(issue imported from #M5466)
Files
any chance to see enhanced List module in 4.2?
hi Ingo
could you add this feature to 4.2?
It would be great if the lists for the record types are separated in tabs. So you see a tab for every record type, that would make it also much faster....
Patch works for me.
I have used ext:list_adv for quite some time. Very usefull feature when fiddling with a lot of records.
+1 to get this in the core.
I suggest to make mod.web_list.pagination = 1 a userTSconfig instead and enable it per default. Then the top level page (cant set pageTSconfig there afaik) would also have this feature. (relevant for admins eg. for the bunch of static_info records). What do the devs say?
This feature is related to #15818 that enables expand / collapse for the list module. Suggestions how to make them configurable the same manner (both userTSconfig / pageTSconfig)?
As I saw this in the 4.3 wiki:
Please try to develop something more in th espirit of HTML. It is possible to have thead, multiple tbodies, tfoot and caption. On tbodies can be set a scroll if wanted.
So HTML has all requisites for making a very nice paged list. Active rows are in the generated page, pending rows can be accumulated in the background, which then makes reloading basically redundant.
Multiple versions of the rows can be shown through multiple bodies (seperator visible and draggable for adjusting size), for example 1st tbody: normal table, 2nd tbody: used elements, 3rd tbody: filtered by search-word, ...
Just examples to unfletch some of the power tables have but nowbody sees.
any sense to make new patch for 4.2 ?
and by the way could anyone explain why it was not included in 4.2 core?
usability of BE is pretty important thing for any CMS. Why core team doesn't care about it?
Uploaded a new and reworked patch to make this bug ready for a core list RFC:
- See attached screenshots for visual impression
- Record browsing is not enabled in multi table view, a link to single table view with labled "Manage all records" is shown instead
- New PageTS parameter mod.web_list.pagination (default on)
- New PageTS parameter mod.web_list.pagination.directPageLinks (default 5, number of links to surrounding pages)
- This patch is as non intrusive as possible and does not introduce any new GET/POST parameters.
- Patch also works in combination with pageTS parameter mod.web_list.listOnlyInSingleTableView
- As usual, all pageTS parameters can set as userTS by prepending with page. (eg page.mod.web_list.pagination.directPageLinks = 7)
Committed to trunk (r5132)
Also available in: Atom
PDF