#108876TableListViewHelper Returns Empty Output Due to Inherited PageContext Language Filtering
Description
I might be missing something, but I’ve been debugging the following issue and wanted to flag it.
The <f:be> ViewHelper in TYPO3 v14 returns empty output for tables with existing records when used in custom backend modules. This is caused by the ViewHelper inheriting the parent module’s pageContext request attribute, which applies unintended language filtering to the database query.</f:be>
*Steps to Reproduce*
1. Create a custom backend module using Extbase ActionController with ModuleTemplateFactory
2. Register the module with the page tree navigation component
3. In the module’s Fluid template, use <f:be>:<br> <f:be tablename="tx_myext_domain_model_item" storagepid="1"></f:be></f:be>
4. Ensure records exist in tx_myext_domain_model_item (multi-language connected mode)
5. Navigate to the Page Module and select a language filter (e.g., only German)
6. Navigate to your custom backend module
7. Result: The <f:be> returns empty output</f:be>
The ViewHelper returns empty HTML output because:
1. The inherited pageContext may exclude the default language from selectedLanguageIds
2. The l10n_parent = 0 constraint is always added when any language filter is active
*Expected Behavior*
The <f:be> ViewHelper should display all records matching the specified storagePid and table, without inheriting language filter settings from other backend modules as in v11,12,13</f:be>
Fast Example in my Extension: https://github.com/eibiflo/cf_cookiemanager/blob/main/Resources/Private/Partials/BackendTabs/frontend.html
Fix that works locally:
In TableListViewHelper::render(), changing line 127 from:
$dbList->setRequest($request);
to:
$dbList->setRequest($request->withoutAttribute(‘pageContext’));
Related Changes:
Feature #108016
Feature #103258
Reviews 1
History 68
-
Florian E. commented <span data-processor="relativetime" data-value="2026-02-06T07:35:08+00:00" > 02/06/26, 07:35 </span>
Georg Ringer wrote in #note-1:
> sounds valid, wanna push a patch?Sure, I can try that, I’m just wondering if this really solves the problem or if it’s just a hotfix in the ViewHelper. Would this affect other things in the backend? Otherwise I’m happy to try the ViewHelper patch, I just wanted to quickly check back whether this is the right approach or if I’m missing something.
-
Georg Ringer commented <span data-processor="relativetime" data-value="2026-02-06T14:42:24+00:00" > 02/06/26, 14:42 </span>
TBH I would need to take a look first as well but it sounds totally valid solution and it would be a perfect start
-
Georg Ringer changed status
NewAccepted <span data-processor="relativetime" data-value="2026-02-06T14:42:31+00:00" > 02/06/26, 14:42 </span> -
Gerrit Code Review pushed patch set 1 for main to change 92738 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-02-07T10:54:36+00:00" > 02/07/26, 10:54 </span> -
Gerrit Code Review pushed patch set 2 for main to change 92738 <span data-processor="relativetime" data-value="2026-02-07T11:08:06+00:00" > 02/07/26, 11:08 </span>
-
Florian E. commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-02-09T06:35:10+00:00" > 02/09/26, 06:35 </span>Applied in changeset commit:96b8e7527679f67e13c2d04378cbd918c2b9629e.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T08:10:49+00:00" > 03/31/26, 08:10 </span>
sounds valid, wanna push a patch?