[FEATURE] Introduce sorting for POI lists #202

Open

Anja Leichsenring wants to merge 2 commits from 13204_sorting into main

pull from: 13204_sorting

merge into: typo3:main

typo3:main

typo3:2.x

typo3:3.x

typo3:12476-import-files-prepare-tests

typo3:12476-import-files

typo3:11518-support-closing-days

typo3:10902-opening-hours

typo3:migrate-to-json

typo3:10243-endless-loop

Conversation 0 Commits 2 Files changed 22 +787 -11

Anja Leichsenring commented 2026-10-09 14:16:20 +00:00

Owner

Copy link

Currently only TouristAttractions have a frontend plugin that lists
records in arbitrary order, and up until now it was alphabetically
by title ascending.
In order to provide editors with an easy way of predefining ordering
in frontend lists, the filtered list and list plugin now carry
a field to define sorting after title (the current behaviour) or by
backend sorting. If the editor applies a sorting through standard
TYPO3 mechanics and the plugin says so, this backend defined sorting
is carried into the frontend.
If two records share the same order number, their placement is undefined
as is the standard for TYPO3. Please mind the limitation for small
data sets, as sorting a large number of records will not be effective.
Also, BE ordering in large folders has serious issues, it does not really
work like expected.
Still, for small amounts of records and patient editors, it is an
alternative to arbitrary title sorting

Resolves: https://redmine.werkraum-media.de/issues/13204
Assisted-by: Claude Opus 5 noreply@anthropic.com
Signed-off-by: Anja Leichsenring aleichsenring@ab-softlab.de

Currently only TouristAttractions have a frontend plugin that lists records in arbitrary order, and up until now it was alphabetically by title ascending. In order to provide editors with an easy way of predefining ordering in frontend lists, the filtered list and list plugin now carry a field to define sorting after title (the current behaviour) or by backend sorting. If the editor applies a sorting through standard TYPO3 mechanics and the plugin says so, this backend defined sorting is carried into the frontend. If two records share the same order number, their placement is undefined as is the standard for TYPO3. Please mind the limitation for small data sets, as sorting a large number of records will not be effective. Also, BE ordering in large folders has serious issues, it does not really work like expected. Still, for small amounts of records and patient editors, it is an alternative to arbitrary title sorting Resolves: https://redmine.werkraum-media.de/issues/13204 Assisted-by: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Anja Leichsenring <aleichsenring@ab-softlab.de>

Dirk Koritnik was assigned by Anja Leichsenring 2026-10-09 14:16:20 +00:00

Anja Leichsenring added 1 commit 2026-10-09 14:16:20 +00:00

[FEATURE] Introduce sorting for POI lists ... ee1ff6266d

Currently only TouristAttractions have a frontend plugin that lists
records in arbitrary order, and up until now it was alphabetically
by title ascending.
In order to provide editors with an easy way of predefining ordering
in frontend lists, the filtered list and list plugin now carry
a field to define sorting after title (the current behaviour) or by
backend sorting. If the editor applies a sorting through standard
TYPO3 mechanics and the plugin says so, this backend defined sorting
is carried into the frontend.
If two records share the same order number, their placement is undefined
as is the standard for TYPO3. Please mind the limitation for small
data sets, as sorting a large number of records will not be effective.
Also, BE ordering in large folders has serious issues, it does not really
work like expected.
Still, for small amounts of records and patient editors, it is an
alternative to arbitrary title sorting

Resolves: https://redmine.werkraum-media.de/issues/13204
Assisted-by: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: Anja Leichsenring <aleichsenring@ab-softlab.de>

Anja Leichsenring added 1 commit 2026-10-09 14:21:01 +00:00

[TASK] Improve documentation with the new flexform field in plugins c21640adb9

Some checks failed

Hide all checks

CI / base-qa (pull_request) Successful in 32s

Required

Details

CI / advanced-qa (82, ^13.4) (pull_request) Failing after 7m7s

Required

Details

CI / advanced-qa (82, ^14) (pull_request) Successful in 7m24s

Required

Details

CI / advanced-qa (83, ^13.4) (pull_request) Failing after 7m6s

Required

Details

CI / advanced-qa (83, ^14) (pull_request) Successful in 7m30s

Required

Details

CI / advanced-qa (84, ^13.4) (pull_request) Failing after 7m0s

Required

Details

CI / advanced-qa (84, ^14) (pull_request) Successful in 7m14s

Required

Details

CI / advanced-qa (85, ^13.4) (pull_request) Failing after 7m14s

Required

Details

CI / advanced-qa (85, ^14) (pull_request) Successful in 7m32s

Required

Details

Some required checks were not successful.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin 13204_sorting:13204_sorting

git switch 13204_sorting

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

Dirk Koritnik

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

typo3/thuecat!202

No description provided.