Pagination (Node) module removes all CCK fields

Happens to me too, tried to set up pagination, which works, but all CCK fields disappear.

Hi there,

Thanks for the feedback, I've identified the issue and I'll try roll out a patch for this as soon as possible.

Hi there,

Thanks for helping me find that, from what I could gather, CCK builds the custom fields you declare, and then attaches them to the body of the content. The issue then, is that pagination does the same thing, and as such was overwriting their display. I've changed the location at which pagination will alter the content, so that CCK can happily do it's thing over it.

As for what that means practically, it will follow the same pagination that was discussed in #321396, namely, only the actual body of the content will be paginated. Additional CCK fields will be present on each page. I believe this is the preferable result for most use cases. If people would prefer that pagination includes CCK fields, let me know, and I'll see if there's enough support for it to offer that as an alternative.

Can anyone confirm for me that Pagination Node now plays nicely with CCK View Reference?

I was having trouble with any custom node type that had both Pagination Node activated for that type (but not used) and a View Reference field linking to a view with paging.

Thanks for this speedy fix. Works like a charm (well, almost - I don't like the "show all" link, but this is something completely different).

No experiences with View Reference though (don't use it).

Hi there,

Not a problem! You can toggle the display of "show all" in the admin settings now too by the way :)

Stupid me, I was so excited it was fixed, I didn't even notice the option. I can delete the css workaround now...

Many thanks again.