Download & Extend

Pagination (Node): Pager controls not showing up

Project:Pagination (Node)
Version:6.x-1.4
Component:Miscellaneous
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

It only shows the display all link but not the individual page links.

Comments

#1

Status:active» postponed (maintainer needs more info)

Hi there,

Do you have a URL where you can show me this behaviour? Also, what sort of paging style are you using?

#2

default: 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.

AttachmentSize
node.png 7.97 KB

#3

Hi 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.

#4

dropshadow is one, http://drupal.org/project/dropshadow, will go through the ones I have and report back.

#5

Hi there,

Thanks for the info, I hopefully will have time next week to knock a bunch of these issues out into an updated release.

#6

subscribe - same problem with acquia_marina theme. Maybe not defined by theme to use pagination? not sure.

#7

Hi there,

Thanks for the update, I'll address this before the next release.

#8

Status:postponed (maintainer needs more info)» fixed

Hi 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!

#9

Version:6.x-1.3» 6.x-1.x-dev
Category:support request» bug report

Thanks! 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.

#10

Version:6.x-1.x-dev» 6.x-1.4

Hi 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.

#11

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.