Project

General

Profile

Actions

Bug #78769

closed

No effect when setting mod.web_list.itemsLimitPerTable and mod.web_list.itemsLimitSingleTable by Page TSConfig

Added by Georg Tiefenbrunn about 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2016-11-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I tried limiting the display of records in list view using Page TSConfig as documenten in https://docs.typo3.org/typo3cms/TSconfigReference/7.6/PageTsconfig/Mod/#web-list-mod-web-list.

Setting mod.web_list.listOnlyInSingleTableView = 1 does work.

Setting mod.web_list.itemsLimitPerTable = 2 or mod.web_list.itemsLimitSingleTable = 2 does not work.

The option "Page TSconfig" in module Info displays the altered values but the list view simply ignores them.

Actions #1

Updated by Michael Oehlhof almost 8 years ago

It works like documented in 7.6 and 8.6-dev.
For which table do you think it won't work?

The settings can be overridden by TCA settings of a table. If ['interface']['maxDBListItems'] is set, this value is used instead.
See https://docs.typo3.org/typo3cms/TCAReference/Reference/Interface/Index.html?highlight=maxdblistitems
This setting is used in the pages table for example.

Actions #2

Updated by Stephan Großberndt almost 8 years ago

  • Status changed from New to Needs Feedback
Actions #3

Updated by Georg Tiefenbrunn almost 8 years ago

Thanks for pointing me in the right direction!

I tried to limit sys_category item list which has no $GLOBALS['TCA']['sys_category']['interface']['maxDBListItems'] nor $GLOBALS['TCA']['sys_category']['interface']['maxSingleDBListItems'] which could overwrite the Page-TSconfig.

Digging through the core lead me to BackendUtility::getModTSconfig and my brain started to work again:

  • User-TSconfig overrules Page-TSconfig
  • $GLOBALS['TCA'][{table}]['interface'] overrlues both User-TSconfig and Page-TSconfig

A nasty snippet in User-TSconfig caused the problem.

Actions #4

Updated by Christian Kuhn almost 8 years ago

  • Status changed from Needs Feedback to Closed
Actions

Also available in: Atom PDF