Closed (fixed)
Project:
Pagination (Node)
Version:
6.x-1.4
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Feb 2009 at 12:48 UTC
Updated:
5 Mar 2009 at 06:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
mundanity commentedHi there,
Do you have a URL where you can show me this behaviour? Also, what sort of paging style are you using?
Comment #2
darumaki commenteddefault: paging
150 pagination
I notice it works with the garland theme, I've tried a few different themes and did not appear with others, it is something to do with theme ? I have more than enough words in the node so it should work.
Comment #3
mundanity commentedHi Darumaki,
Thanks for the additional information, can you point me in the direction of a theme (or two) that don't work? Should be a quick fix if I can reproduce it reliably.
Comment #4
darumaki commenteddropshadow is one, http://drupal.org/project/dropshadow, will go through the ones I have and report back.
Comment #5
mundanity commentedHi there,
Thanks for the info, I hopefully will have time next week to knock a bunch of these issues out into an updated release.
Comment #6
CarbonPig commentedsubscribe - same problem with acquia_marina theme. Maybe not defined by theme to use pagination? not sure.
Comment #7
mundanity commentedHi there,
Thanks for the update, I'll address this before the next release.
Comment #8
mundanity commentedHi there,
This has been resolved in the latest dev update (should be dated Feb 18th I believe). A 1.4 release should follow in a few days if you want to wait for the "official" version. Thanks for your help!
Comment #9
carbonpig-1 commentedThanks! The pagination now works, but the Table of contents is broken...
It shows Page 1 (by title), 1, 3, 1, 4, 1, 5 as the default pattern....
I don't know why it's only picking up every other page #, but that's the current bug.
Comment #10
mundanity commentedHi there,
Oops, was hoping no one would notice :). Download the official 1.4 release, there was a bug introduced in dev that caused that, which was corrected in the 1.4 release.