If core body field is not used for custom content type and another field named field_body is used instead paging links will not show up.
I'm not sure if this should be files as bug report but it will definitely save people time trying to figure out why page links won't appear (adjusting filter order will not fix this).

Could the following be added to the README.txt for Paging?
Paging does not work with CCK content types where core body field is not used.

Also on the project page installation instructions are misleading - enabling paging for content types also applies in D6 version. So when/if this makes to the dev version stage these instructions should be updated.

Comments

Gurpartap Singh’s picture

Gurpartap Singh commented

Drupal 6 version is merely a port with some per content type settings setup. A stable release is expected after a few issues are cleared off. Till then, no Drupal 6 production support, no upgrade paths.

I'll see what I can do with CCK support further.

Thanks!

Gurpartap Singh’s picture

Gurpartap Singh commented
Status: Active » Fixed

Added the statement under "Limitations" in README.txt.

mike15’s picture

mike15 commented

Sorry, just to clarify your statement earlier. Are you not planning to offer upgrade path from 5.x to 6.x?

It appears that with the current 6.x release, the upgrade doesn't work.

Fairly big issue for me as I've been using this module for quite sometime... a lot of my contents utilize
and after my trial upgrade, I see <!--paging_filter--> on each page (not hidden) and <pagebreak> is not working...

Thanks in advance.

Gurpartap Singh’s picture

Gurpartap Singh commented

There's no such change that needs an upgrade from Drupal 5. Go ahead, upgrade to Drupal 6 :)

If you are getting this http://drupal.org/node/331847 error in the upgrade, you can ignore it. It isn't going to break anything. Anyways that error is also fixed in current 6.x-1.x-dev release and needs to be fixed for Drupal 5 release.

mike15’s picture

mike15 commented

That makes me feel a little better knowing that the support is there and I can consider upgrading.

In regards to upgrade from 5.x to 6.x, it is not functioning correctly for some reason and it doesn't appear to be related to the issue you indicated. I will open a separate support issue to track that.

Thanks for your prompt response.

Status: Fixed » Closed (fixed)

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