Where the page sizes live #

Read this page if you want to change how many rows a list in the administration interface shows, or if you overrode a list template or module that used to have its page sizes written into it. Every paged list in the admin now takes its page size from a setting, so a site can choose its own without editing a template or a module. This page is the index of those settings.

In short #

Change a page size in one minute #

Show 50 sections per page instead of 25:

# settings/override/admininterface.ini.append.php
[PaginationSettings]
ItemsPerPage[section/list]=50

php bin/php/ezcache.php --clear-all --allow-root-user

Reload section/list: it shows 50 rows.

The settings #

Most of them live in one block, admininterface.ini [PaginationSettings], keyed by the module and view that draws the list, so you can find a setting from the address of the page it governs.

[PaginationSettings]
DefaultItemsPerPage=25
ItemsPerPage[section/list]=25
ItemsPerPage[shop/archivelist]=50

The four explayouts_ui entries are shipped by that extension's own settings/admininterface.ini.append.php, so using it does not mean adding entries to the kernel's settings by hand.

These five predate the block and keep settings of their own:

Override any of them per siteaccess like any other setting — settings/siteaccess/<name>/ or settings/override/.

Deliberately not paged #

shop/preferredcurrency is a drop-down for choosing one currency, not a list of rows. Paging it would make it unusable.

Where the reading happens #

expAdminPagination answers all of it:

expAdminPagination::limit( 'section/list' );          // one size
expAdminPagination::sizes( 'shop/currencylist' );     // the sizes a selector offers
expAdminPagination::chosen( $view, $preferenceName ); // size, choice, sizes
expAdminPagination::offset( $Params );                // the page asked for
expAdminPagination::page( $rows, $offset, $limit );   // one page of a list in memory

offset() reads the user parameters as well as a declared Offset, so a list can be paged without changing the module definition it belongs to.

page() is second best and says so: it bounds what is drawn, which is what takes a page of hundreds of rows down, but not what is read. It is used where the model has no fetch that takes an offset and a limit. Where one exists it is used instead — role/list, section/list, state/groups, oauthadmin/list and the locations tab all page in the query.

One size, or a list of them #

Two shapes appear above, because two kinds of screen exist.

A screen with no items-per-page selector takes a single integer:

[LocationsSettings]
LocationsPerPage=25

A screen with a selector takes the list of sizes it offers, the first being what someone who has never chosen gets:

[RoleSettings]
RolesPerPageList[]
RolesPerPageList[]=10
RolesPerPageList[]=25
RolesPerPageList[]=50

The list is also what bounds the query. A size that is not on it cannot be asked for in the url either, so lengthening it is how you allow a larger page, and nothing else can.

Both shapes fall back to their default when the setting is emptied or filled with something that is not a positive number — a list with no usable size in it would otherwise divide by zero further down.

What the preference stores #

The selector remembers a choice per user, in admin_role_list_limit and admin_rss_list_limit.

role/list stores the position in the list, counting from one — not the size. That is what it has always stored: the values 1, 2 and 3 meant the first, second and third of a set of sizes written into the module. Keeping the meaning means a site that changes RolesPerPageList keeps everyone's choice rather than resetting it, and no stored preference has to be migrated.

rss/list stores the size itself, and ignores a stored size that is no longer on the list.

What this replaced #

role/list had the sizes written into the module:

switch( eZPreferences::value( 'admin_role_list_limit' ) )
{
    case '2': { $limit = 25; } break;
    case '3': { $limit = 50; } break;
    default:  { $limit = 10; } break;
}

and written again into the template, as choose( 10, 10, 25, 50 ) for the selector. Two lists that had to agree by hand, and no way to change either.

rss/list had eZRSSListPager::limits() returning array( 25, 50, 250 ).

Checking it #

Changing the settings and reloading is the test:

Run after any change to a settings file:

php bin/php/ezcache.php --clear-all --allow-root-user

Read the shipped values with grep -n -A40 "^\[PaginationSettings\]" settings/admininterface.ini.

Related pages #

• Paging, sorting and page sizes in the administration interface
• Role and policy paging and Locations tab paging and sorting
• September 2026, first half: 15 September
• Changelog 6.0.15