[TYPO3-core] RFC #9861: Second page of results in list-module with ordering flaw

[Christian Kuhn]

Hi.

I found a solution to solve this bug without additional db queries. Here 
is a new RFC with proper description.


This is a SVN patch request.

Type: Bugfix

Branches: trunk, 4.2-branch

Bugtracker Reference: http://bugs.typo3.org/view.php?id=9861

Problem:
If you have more than 20 content elements you get browser [21 - xx]
If you click you are on the second page.
The first item (is item no.21) misses an up-icon for sorting.
If you click on the up-sorting of item no.22 it will be no.1 and not 
visible on this page.
See attached screenshot.

Solution:
For proper sorting of the first two elements on page > 1 the uids of the 
last and second last elements of the previous page must be known and 
initialized to $prevUid and $prevPrevUid.
The patch lets makeQueryArray() fetch two more rows (LIMIT 18,103 
instead of 20,101), and initializes the two variables with the uids from 
the first two rows.


Cheers
Christian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: list_bug.png
Type: image/png
Size: 43873 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090120/1a40661a/attachment-0001.png 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 9861_01.diff
Url: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090120/1a40661a/attachment-0001.txt