Pagination for CCK Field

Why not use the node's "Body" field instead of CCK textarea?

The better but rather difficult method would be to convert existing nodes from textfield to body field. And the easier but not recommended method would be to hack paging.module. It IS possible, but will require significant changes and testing to code for all the functionality to work properly. Now I think the former method would be easier. :)

Hacking paging to support for an existing CCK field would be really really bad, unless you are willing to maintain the change through every version of paging that is released. I would still say that it's still better to convert from textfield to body field. Even if you have thousands of nodes, you can process them easily in batches. At least you'll be worry-free after the job's complete. But if you are unsure about performing a successful conversion and are willing to hire someone, you can offer a bounty for the job in Paid Services forum.

I recently had the job of changing a node type's body CCK field over from CCK to Body field of the node, for the purposes of using pager, and found it surprisingly easy:

1. First re-enable the node body by re-adding the 'Body field label' to the Node settings 'Submission form settings'.
2. Run the command to copy the cck column contents to the related node body column:

UPDATE `node_revisions`, `content_type_custom` SET body = content_type_custom.field_custom_body_text_value WHERE node_revisions.vid = content_type_custom.vid

3. Goto the Manage fields of the custom content type, and Delete the custom body field.
4. Update any styles and views to use the new field.

Done!

Hope that can help someone.