request previous page next page links in cck

How do you envision this working? How would CCK know what the next page and previous page are? Node reference fields?

This could get very complicated since there are lots of different ways you might want to chain your nodes together. You said you couldn't get category to work. I can't tell exactly what problems you ran into, but category worked great for me. Category is a complex application, so it took some experimenting to find out how to best use it. Here's how I made it work with CCK to get back/next links and a table of contents on the parent pages:

1) Be sure to install category menu and category transform.

2) If you want your cck nodes in their own grouping, create a container for them. When you create the container, indicate that you want back/next links on the categories inside it and that you want a TOC (table of contents) used and set the depth of the categories inside the container to be more than 0. You will probably want to add the container to the menu, too. If you want to use an existing container, make sure it has those options set.

3) Create your cck node.

4) Edit the cck node, and click on the category tab and indicate you want to add it to the category outline. While in the category tab, make sure you indicate that it should be in the container you just created. Once you have more than one node in there, you will also have the option to select a parent for the node.

5) You should now be able to go to the container and see a table of contents listing the node you just created. If you view the node, you will see back/next links (if there are other nodes in there) and an 'up' link.

6) For even more options, you can install category views which allows you to create a views table or listing of the nodes that shows up on the parent page instead of the default teaser list. You can put the node title and date into the view, plus whatever cck fields have been views-enabled (that part of cck is still under construction).

You have to play around with the category settings since there are lots of different options. You can choose multiple parents and even distant parents (categories in other containers) for the construction of the outline and back/next links (you have to set this all up in the container).

Just wanted to point out a couple other ways to accomplish this (and I'm not downplaying your request or saying it might not be desirable to add at some point, just pointing out there are several ways to do this already):

1) Use the book module. It is in core, which seems to be your concern, and it is the way you add back/next links to any other module that needs them. Create a book for your cck content type and use the add to outline feature.

2) Use the views module. It is not in core, but is clearly going to be closely integrated into cck. To do this, go to admin/views and create a new view.

In the 'Page' section check that it should be displayed as a page, give it a url, select the option to display it as a full node, and set it up to show one node per page.

Ignore the 'Fields' section (not needed if you are using the node display mode) and jump to 'Filters'. Add the following filters (plus any others you want to use to limit it): Node:Published and Node:Type (mark the cck content type).

Jump to the 'Sort' section and add in the fields you want to sort on.

Save the view, then go to the url you gave it and you will see one node on a page, with back and next links.

Currently you won't see any cck fields in the list of fields, filters, and sorts, but that will be coming when the cck views support gets re-enabled. You can still see how it works now by using node fields for filtering and sorting.

I don't get the title of the view at the top of every page, I get the title of the node (did you put a title into the view? If so, take it out and you will just get the node title.)

If you have book enabled, you should see a tab called "outline" on every node. Select that tab to add the node you are looking at into the book. It should work for any type of node.

Karen's solutions seem more appropriate than tying this behavior to CCK at all.

The book module will be in 4.7 without question.

Thank you.