Clearly something like this can be achieved using Views and the pager but I'm not sure that will work with what I have it in mind.
The behaviour would be that the visitor is first presented with a summary list of items; this list would be rendered using a View. The visitor would then select one of these items and the relevant detail page would be shown with the next/previous links (as per the above example).
So this is not stepping through a series of pages from beginning to end as such, rather jumping in at a particular page and then moving backwards and forwards.
I have two thoughts on how to achieve this:
1/ display the detail page as the actual Node and somehow use a Block View to determine the next/previous links. But I am unsure how to feed the Node id into the View and have this work out the next/previous Node ids.
2/ display the detail page as a single View page (not using a pager) and somehow have this return the next/previous Node ids in the result set. But again I cannot think how to achieve determining the next/previous Node ids, based on the current Node.
After upgrading Drupal core from 7.2 to 7.7, I now receive this error message on every page:
Notice: Undefined index: secondary-links in menu_block_view() (line 462 of /var/www/modules/menu/menu.module).
I noticed that the Secondary Links menu was renamed to "Secondary Menu". I did have the Secondary Links menu block enabled before upgrading, but after upgrading it obviously doesn't exist anymore. I moved the "Secondary Menu" block back to the region I had the Secondary Links block, but the error persists.
Well, since I'm still working on learning the Drupal syste, I upgraded my 7.4 installation to 7.7 - and the upgrade worked perfectly the first time. I followed the instructions provided on the upgrade 7.x page. Before installling 7.7, I dutifully erased all of the core files except for the /sites folder.
(See below for actual code)
I have two sections of code, the first is marked off with <!--[if !IE]><!--><!--<![endif]--> and the second with <!--[if IE]><![endif]-->. IE works as desired and doesn't not render the first section. Firefox, however, stops recognizing the conditional comment midway through and starts rendering some of the comments. In the view source, I can see exactly where FF decides to start rendering the comment and displays some of the comment followed by a red(instead of green)<![endif]-->. This completely breaks the page in FF and I'm trying to figure out what is causing it to start recognizing the comments.