#109049Search option in Web > List should respect user's wish to be presented
Description
The option to show the search box within a folder:
clipboard-202602210923-o6588.png
is only respected when the corresponding folder contains at least 1 record. If the page does not contain any records, then the search box is not presented, which would make sense if the search would only search within that folder, but the search form allows to search recursively:
clipboard-202602210925-d6dot.png
As such, it is illogical from a user perspective not to show the search box.
If fixed it in TYPO3 v11 with following patch for EXT:recordlist:
--- a/Classes/Controller/RecordListController.php 2024-07-01 13:35:27
+++ b/Classes/Controller/RecordListController.php 2024-07-01 13:34:26
@@ -268,7 +268,7 @@
}
// search box toolbar
- if (!($this->modTSconfig['disableSearchBox'] ?? false) && ($tableOutput || !empty($search_field))) {
+ if (true || !($this->modTSconfig['disableSearchBox'] ?? false) && ($tableOutput || !empty($search_field))) {
$beforeOutput .= $this->renderSearchBox($dblist, $search_field, $search_levels);
}
Now, the corresponding patch for TYPO3 v12 would be something like that:
--- Classes/Controller/RecordListController.bak.php 2026-02-19 11:09:17
+++ Classes/Controller/RecordListController.php 2026-02-21 09:27:45
@@ -186,7 +186,7 @@
$pageTranslationsHtml = $this->renderPageTranslations($dbList, $siteLanguages);
}
$searchBoxHtml = '';
- if ($this->allowSearch && $this->moduleData->get('searchBox') && ($tableListHtml || !empty($this->searchTerm))) {
+ if ($this->allowSearch && $this->moduleData->get('searchBox')) {
$searchBoxHtml = $this->renderSearchBox($request, $dbList, $this->searchTerm, $search_levels);
}
$clipboardHtml = '';
Please either change this behaviour or explain why this UX was changed starting from TYPO3 v11 so that I can at least argue about the odd behaviour in TYPO3 Core.
I must admit my editors are right in that context, it’s odd not being to show the search form in that context, and the global search is of course always present but that’s a global search which behaves slightly differently than the search form in Web > List.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
Files 2
History 6
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-02-21T08:38:57+00:00" > 02/21/26, 08:38 </span> -
Garvin Hicking changed category <span data-processor="relativetime" data-value="2026-02-21T08:39:28+00:00" > 02/21/26, 08:39 </span>
-
Xavier Perseguers changed Related to #105313 <span data-processor="relativetime" data-value="2026-02-21T08:58:56+00:00" > 02/21/26, 08:58 </span>
-
Xavier Perseguers commented <span data-processor="relativetime" data-value="2026-02-21T09:00:45+00:00" > 02/21/26, 09:00 </span>
Indeed, fixed in TYPO3 v13, double checked the code wasn’t changed either in main branch on git.
=> To be closed as TYPO3 v12 is in priority security-fixes only.
-
Xavier Perseguers changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-02-21T09:33:57+00:00" > 02/21/26, 09:33 </span> -
Garvin Hicking commented <span data-processor="relativetime" data-value="2026-02-21T09:34:42+00:00" > 02/21/26, 09:34 </span>
Thanks for checking and relating!
I believe this was fixed in v13 already, can you verify? Thanks.