Closed (outdated)
Project:
Drupal core
Version:
6.x-dev
Component:
database system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Feb 2006 at 15:01 UTC
Updated:
2 Mar 2016 at 22:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
markus_petrux commentedGood catch. It looks like pager_load_array should return elements in $new_array only for elements set in (say) $pager_page_array ?
Comment #2
markus_petrux commented???
Comment #3
Bèr Kessels commentedit fixes only half of the issue.
We now see ?page=0,1 but still not the expected ?page=12,1 (in case I gave $element arg. as 12)
Bèr
Comment #4
markus_petrux commentedThe values for the var $page are page numbers, not the element, which is the position the internal pager array.
The patch seemed to work here. :-?
Comment #5
Bèr Kessels commentedPreviously the argucment $element was
« An optional integer to distinguish between multiple pagers on one page »
Which means that if i do:
pager_query($query, 10, 12)andtheme('pager', NULL, 10, 12);, i have a pager with a unique pager ID of 12.That means that by calling that the pager 12, I can identify it from other pagers on that same page. (like a pager in a block, or the pager for comments under a node).
It is not used very often, because hardly anyone prints more then one pager on a page. but still, he option is there, and therefore should work as expected.
Comment #6
markus_petrux commentedWhat about this one?
It provides an array to map $page_id to $element. Where $page_id can be anything and $element is always a zero based pointer to the internal $pager arrays.
Comment #7
markus_petrux commentedSorry, previous patch had a couple of debug statements in place.
If too complex, this could also be considered a bug on the calling process side. Why would you use non-continuous zero based pager ids? maybe
Comment #8
flk commentedrerolled against head
Comment #9
drummThe existing behavior seems to work and is intended. This patch looks like an improvement, but we don't need to change URLs for Drupal 5.0.
Comment #10
zigma commentedAre we planning to fix it in 5.x?
On another note. Pager does not seem to take care of fragments in the link. This breaks pager feature when i have tabs where each tab is distinguished by fragment identifier.
The pager link ignores fragment identifier and therefore always sends me to first tab.
Any resolution?
Comment #11
bdragon commentedAutopatch Results:
(Stripping trailing CRs from patch.)
patching file includes/pager.inc
Hunk #3 succeeded at 108 (offset 1 line).
Hunk #4 FAILED at 117.
1 out of 4 hunks FAILED -- saving rejects to file includes/pager.inc.rej
Comment #12
dpearcefl commentedIs there any interest in this issue any longer?
Comment #13
dpearcefl commentedIs there any interest in this this issue any more?