Maybe this is the intended behavior, but it sounds like a bug to me. After creating a pager based on a view, the pager appears at the bottom of any node of the chosen type (at least, I saw that with story node types). That is, it also appears on nodes that are not included in the view.

Maybe I'm missing something about using parameters. I use Views 5.x-1.5. Created a view with a filter based on a taxonomy term. The pager actually returns only the nodes in that view. I thought it was great until I saw the pager in a node in a different category.

Comments

eaton’s picture

Status: Active » Fixed

This is fixed in version 1.3a of custom pagers -- when the list of nodes is retrieved, if the current node isn't in it, the pager won't display. Thanks!

Anonymous’s picture

Status: Fixed » Closed (fixed)