pagination by page-break/heading

> would it be possible to insert a pagination point manually?
> Something like the Drupal page break? Eg.

Grrr... drupal ate my page break. Here it is again: <!-break->

Hi there,

Thanks for the feedback, I definitely want to add something like that. My current plan is to make it an optional choice (page by threshold, page by manual break, page by both). Beyond that, I was thinking some sort of jquery widget to pull the node + page headers (mini-menu). I'll try add it to the next major release.

Fantastic!
I think this will be a 'must have' module for many people.

mundowen - thank you so much for working on a D6 port, fantastic!

-Anti - great suggestions, having both a manual- and a threshold option available would be awesome.

I would like to add an additional suggestion. It would be wonderful if the pagination URL parameter (page=1) could somehow be reflected in the page title (<title>Some Page Title - Page 1</title>).

Cheers.

Hi!

Thanks for the feedback, I'll definitely see if that is possible, I don't see it being much of an issue. Just to let you know Paging does provide a lot of this functionality apparently (although I think you have to get the dev version). I'll continue to improve this module until they have an official D6 release, and re-evaluate at that point as to whether we're just doing the same thing.

If paging ever does get into D6 beta (I doubt it), will that be a problem?
You won't be asked to merge your module or drop it, or anything will you?

Hi Anti,

Well, I'm mainly worried about being a good citizen :) If the feature set is weak, or there are severe issues with it I don't mind keeping up development on this, I just didn't want to duplicate it if the maintainer is serious about keeping his module going. I'll try to get a version going with the features you mentioned (and a few others) by next week. Thanks for your interest!

> by next week

Really?? Wow.

It's taken a year and a half just to add a couple of patches to the original paging module. The thing is, the developer is still very busy around the forums and with other modules. It's not as though they have left Drupal; just that the module isn't being worked on heavily.

Personally I'd rather use a a paging module which is active development, even if it completely duplicates one which already exists. I think it would be very unfair of the developer of 'paging' to turn around and demand that you merge them.

This already happened to me once, where development of a new module I needed was asked to be halted because it duplicated the function of an older one. However, the older was not under serious development, and it was inferior too.

@Anti

As promised, version 1.1 implements manual paging [ pagebreak] or [ header = page header]. Headers are also available under auto paging while you are updating/creating a node that has been activated.

As well, a table of contents style of display has been added, and admins can choose between displaying the default pager, table of contents pager, or both.

@rrlange

Unfortunately I wasn't able to add the title change. Apparently drupal uses the same title for the content as well as the browser title. So adjusting one adjusts both. I'll see if I can work around it, but nothing seemed obvious when I went to implement that feature.

OK, so now could you make it so that when clicking 'next', the new page does a jquery slide-in?

lol... only kidding!
Wow... awesome work, and thanks a billion. This is really going to come in useful.

Unfortunately I just downloaded views tonight and I'm trying to get my head round that monster.
But I am very much looking forward to help test your module, probably before the weekend.

Cheers!

Ha, I was thinking of adding some optional candy like that, I may yet just link to various different "implementations" of different effects and such. I think I'd prefer to keep the core module clean though, and have people customize those portions. But like I mentioned I would like to have a collection of effects and instructions on how to throw them in there easily. Good luck with views, I'll be glad to hear any feedback you have (although if you downloaded 1.1, make sure to grab 1.2, it fixes a minor bug I introduced by fixing another bug... typical :) )

There is an awesome new module which does jquery node slides:
http://drupal.org/project/slider
However, the downside is that it loads the group of nodes at once.

That's ok for a handful of pages of light content, but pagination is
far more robust for the usual amount of content in.

By the way, have you tested how your module works with the 'book' module?
Will we get a 'mini-book within a book', or will it all just horribly break?
That's one thing I want to test at the weekend.

The other thing I want to test is, how does pagination affects attachments?
Are the attachments just on the first page, or do they display on all pages?

Cheers

Hi,

That looks like a fun project, and definitely the kind of add on I wanted to offer as separate options. It's related in a way to your book/attachment question. Basically the module will take the body content of a node (since this is typically the main bit) and paginate that. So anything else will be left "as is" on the page.

To give a quick example, if you setup a new node "Extended Blog", and added say two CCK image fields to it, so every blog post you made would have two images. If you then paginated an Extended Blog post, only the actual body would change, the two CCK images associated would remain in the same position on every page. In the book module example, if you paginated your book's pages, it would be in essence a dual pagination (paginate through page nodes, and paginate within page nodes).

I'm new to Drupal so I haven't had a chance to take a look back as extensively as others might have, but it looks like previous pagination was mainly (like slider in theory) stitching together various nodes (this is essentially what the book module does too). What I envisioned was for people who perhaps had a longer article/blog entry on their site, and didn't want to go through all the trouble of breaking it up into separate nodes and manually figuring out which nodes went with what, and having to redo them all if they decided they wanted amount of content on a particular "page".

Anyhow, I'll see how the week goes, I was hoping to get a few jQuery style options in that people could tack on quickly for fun by next week, but don't hold me to that :)