Any chance of some documentation on this? I'm loathe to start installing loads more modules when I can't see how to use them 'off the bat', so to speak.

Otherwise sounds like this will be much appreciated by the community. Will it support CCK content types, and maybe Contemplate (if and when it gets ported)?

Comments

eaton’s picture

eaton commented

Working on the docs. :-) And it should support all node types; there's nothing node-type-specific in it, really.

niklp’s picture

niklp commented

Coolio!

I was just hoping for an initial scenario of how it works. Does it impact on anything in any bad way, like performance etc? Or is it as good as it sounds? Easy to set up, is it?

Also you don't mention specifically where the pagers are being used in your live example (which looks like a pretty tasty site by the way, flash and adverts aside) - can you elaborate on how the pagers are used there?

Thanks chap, looking good.

eaton’s picture

eaton commented

It's being used to generate the navigation arrows on the photo pages, and the individual forum topics. There is a potential performance hit if you're paging through a view that contains, say, dozens of thousands of nodes: it temporarily loads that list of node IDs, then cycles through them to determine where in the list the current node is. Then, it creates a link to the nodes immediately before and after it. For most sites it shouldn't be an issue, but I'm investigating intelligent caching approaches and other ways to optimize it for the super-heavy load scenarios.

eaton’s picture

eaton commented

Regarding setup, it works like so:

You create a new pager, and specify what kinds of nodes it applies to. Then, you specify what view should be used to generate the context that the pager will be stepping through. Then you say whether you want the pager to appear above or below the node body (or both), or whether you want it to appear in a dedicated sidebar block.

Each pager can also be themed individually -- allowing a simple 'next/prev' text link on one node type but elaborately themed arrows and rollover icons for image nodes. It's now also possible to have multiple pagers per node -- one that pages through 'all nodes by current node's author' and another that pages through 'all nodes that share the current node's main taxonomy term', both displayed on the same page.

ubersoft’s picture

ubersoft commented

I have attempted to document (kinda, sorta) Custom Pagers (as I understand it) in this forum post. It's not my best work, but it was a first pass. Also, the information in it is suspect, since I've yet to be able to get it working on my live site.

eaton’s picture

eaton commented

ubersoft, zounds. thank you for the work on getting that document written. I'll take a quick look at it now, and attempt to put together some 'official' docs that clarify some of the questions. Thanks!

eaton’s picture

eaton commented
Version: 5.x-1.2 » 5.x-1.4
Status: Active » Fixed

A README.txt file is now included with the Custom Pagers download -- it should explain things a bit better.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)