Project

General

Profile

Actions

Bug #16580

closed

"pointer" error in tslib/class.tslib_pibase.php

Added by Dietrich Heise about 18 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2006-09-20
Due date:
% Done:

0%

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

Description

Hi there,

there is a Problem with the "pointer" in the function pi_list_browseresults.
The problem is that the pointer never will be set to '0'.

If I go to "page 2", the pointer is set to "1",
if I go to "page 3", the pointer is set to "2",
but if I go back to the first page, the pointer is not set to any value, that is not good, I expect a "0" here.

(issue imported from #M4254)


Files

Actions #1

Updated by Dietrich Heise about 18 years ago

the first patch does not correct the "< perv" link in the paging

Actions #2

Updated by Rupert Germann about 18 years ago

IMO it is good like it is now. With your patch there would be 2 pages with different parameters showing the same content: The first version would show the first page of the list without a pointer parameter and the second one would show the same content with &tx_plugin[pointer]=0

that will cause problems with indexed_search (double results) because the page is cached two times.

Actions #3

Updated by Dietrich Heise about 18 years ago

My problem is:

I store the search/filter options the user made for the listing in the user session.
so if the user returns the old list can be displayed again.
That works very good, but the first page is only accessable the first time, because I can't check if the pointer is set to '0' on the first page the pointer issn't set, so the last pointer from the session will be used.

IMHO all lists where filter options and a pointer is used, are uncached and the uncached pages are never indexed by the indexed_search.

Actions #4

Updated by Sebastian Böttger almost 16 years ago

I also have this problem in 4.2
You can correct it, by changing the $pointer / $a null or '' if/else statements to $pointer/$a 0

Actions #5

Updated by Alexander Opitz over 11 years ago

  • Category deleted (Communication)
  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • PHP Version deleted (4)

The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #6

Updated by Alexander Opitz about 11 years ago

  • Status changed from Needs Feedback to Closed

No feedback for over 90 days.

Actions

Also available in: Atom PDF