Hello, thanks for this great theme, I like it very much.
However, I find that a pager appears in the comment region, it should not be shown for 1 comment.
To my understanding, pager will only be shown if the number of comment exists the setting limits (e.g. 10 comment / page).

So, I switched to Zen theme and Garland theme. The pager did not show as normal.
I have created another sub-theme for test, the pager appears.

I double check the STARTUP KIT procedure and even compare the source code, templates...etc., but no luck.
It is very strange. Please have a look the attached snapshot for your reference.

Could you please have a look and let me know how to fix it?

Thanks and Rgds,
BadBUTA

CommentFileSizeAuthor
2011-03-20_0302.png24.79 KBbadbuta
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

badbuta’s picture

I just find this issue also exists in different region (e.g. pager in front page). i.e. The pager shows 6 page.

badbuta’s picture

Status: Active » Closed (cannot reproduce)

I forget what I did but it is normal now. Thanks

parka’s picture

I'm having this problem as well, in my own customized theme and default Garland.

Seems like the pager under comments is showing the same number of pages from the promoted stories.

I've a Views created that filters in those promoted stories as well, showing the same pager - when I turn the pager off, the comments pager also disappears.

yang_yi_cn’s picture

Status: Closed (cannot reproduce) » Active

I have the same issue

yang_yi_cn’s picture

Component: Miscellaneous » Documentation
Status: Active » Closed (duplicate)

ok, I figured it out.

It's because the comment-wrapper has a pager theme function, which is normally empty when there's no enough elements for the pagers.

However, it's possible that there are other modules also generates a pager on the same page, in such case, there will be a conflict in the pager namespace if the pager ids are the same (all 0 by default). It's very likely to happen when there's a view that has a pager on the same page.

Similar issue is described in #1450454: pager disappeared when i using views_embed_view in parent views's field tpl file in Views' issue queue.

In my particular case, I'm using views_get_view() to get a view, set the items_per_age, and executed it programtically to get some values I need. However, that also triggers the pager function and causing the problem. I remove that view from this page to fix the problem. But it's also possible to set the "pager id" to a different number in the Views UI (Views 3.x) to avoid the conflict.

ekidman’s picture

Just confirming that the solution in #5 works for me. Changing the "pager id" for one of the pagers eliminates the conflict.