Bug #88159

PaginateController does not respect offset from original query

Added by Chris Müller 3 months ago. Updated 3 months ago.

Under Review
Should have
Target version:
Start date:
Due date:
% Done:


TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


I have an own find method instead of findAll() in a repository which I call from the action of a controller and set an offset in it (for example offset = 1). The paginate widget now renders the items on the first page correctly (e.g. items 2-5 when showing 4 items per page). The seconds page instead will show the items 5-8 instead of 6-9 (so item 5 is shown twice).

This is because the indexAction of the PaginateController does not respect the offset of the queryResult object.

Example for find method in repository class:

public function findAllExceptFirstEntry()
    $query = $this->createQuery();

    return $query->execute();

Example for usage of paginate widget:

<f:widget.paginate objects="{items}" as="paginatedItems" configuration="{itemsPerPage: 4, insertAbove: 0, insertBelow: 1}">
        <f:for each="{paginatedItems}" as="item">

Background: I am using this because I have a top record (first record) which is shown differently from the other records (only on first page). So I am calling in the list action an own implementation of a find method in the repository which sets the offset in the query to 1.

I will provide a patch shortly.


#1 Updated by Chris Müller 3 months ago

  • Description updated (diff)

#2 Updated by Chris Müller 3 months ago

  • Description updated (diff)

#3 Updated by Gerrit Code Review 3 months ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/60487

Also available in: Atom PDF