I like the community/interactive features of Drupal (blogs and such). But I have yet to see a major/professional/big/quality site use drupal to post "formal articles". An example of what I mean as a formal articles is this:

http://www.sitepoint.com/article/developers-writing-guide

Are there any drupal sites publishing mainly formal articles and not blogs/news? I'd love to learn about how they structured the taxonomy.

Thanks!

Comments

venkat-rk’s picture

www.linuxjournal.com is a good example of using Drupal for articles. Here is an example: http://www.linuxjournal.com/article/8298

And, if you use the book.module to build your articles, you automatically get the previous and next pages, plus the printer-friendly output.

fkdsfodsf’s picture

This is just getting stupid.

I've been told by about 10 people not to use books.

One example:

"Do not use books! They are only for storing nodes in a tree-like hierarchy - you won't be able to assign categories to your nodes if you use books, because the book module is not compatible with taxonomy."
http://drupal.org/node/19627

More and more it is becoming apparent that drupal is a bloated blogging tool rather a do-it-all cms.

/frustration :(

Steven’s picture

you won't be able to assign categories to your nodes if you use books, because the book module is not compatible with taxonomy.

This is completely wrong as the original thread's responses indicate. You can create vocabularies for any node type, and any node type can go into the book.

--
If you have a problem, please search before posting a question.

fkdsfodsf’s picture

So should I use stories or books for formal articles?

Prometheus6’s picture

Use stories for your articles. You may want to use books to organize them...for instance, if you're making a monthly ezine you could add your articles to book for each month.

I feel like I want to comment on the "bloated blogging tool." Drupal is (to me) a CMS construction kit with a blog-like default configuration. This is a developer's viewpoint, of course, but I can tell you there's very little that can't be done with Drupal's API...my biggest problem is I keep thinking of cool things I want to try in addition to the things I have to do.

sepeck’s picture

You should use what works for your site. I use currently don't use the book module for my sites, but I am testing it for posible use. You should try it and see if it's capabilities fit what YOU are developing. As Steven said though, you can catagorize anything.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

daniel read’s picture

I use Drupal side-by-side with a formal-article-based, magazine-style site (see my sig for link).

I publish the magazine side as static HTML files, and I use CityDesk for templates/content management; CityDesk publishes the site to the server as HTML files.

The other half to my site is a community-based publishing platform site powered by Drupal. I've given serious thought to merging the magazine site into Drupal and publishing everything in Drupal. It would be great to have my two halves merged into a common template.

I'm sure Drupal can do the job, but I'm fairly certain that I would need to do a lot of template and block tweaking and code customization/module development to have all the tweaks I would want. My existing Drupal template could use polishing as it is, but I'm just one guy, and the visual design aspects of web design is not my strongest skill anyway.

The main things that keep me from taking the plunge are inertia and limited resources. Given the huge amount of formal article content I have at this point, converting it right would be a big job. Someday...

Dan

---------------------------------------------------------------
developer.* - The Independent Magazine for Software Developers
http://www.developerdotstar.com

jesusphreak’s picture

Dan, what template is the drupal part of your site based off of? It looks like a modified Blue Marine theme, but I'm not sure.

Thanks :)

Nice site, btw...its why I ask.

I'm also very interested in what modules you used to get the "e-mail this page", "quote", and "printer friendly page" functions. They are more or less exactly what I need.

Thanks a lot Daniel.

daniel read’s picture

Hi jesusphreak,

If my memory serves, that is based on Blue Marine. I changed the colors some, messed with the fonts and the placement of a few of the elements. There's much more that I'd like to do.

I don't recall the exact module names for the three features you asked for, but if you scroll through the modules list you should be able to find them pretty easily. They use the same or similar names as the links--something like emailpage, quote, and printerfriendly are the module names.

Thanks for the compliment on the site.

Dan

---------------------------------------------------------------
developer.* - The Independent Magazine for Software Developers

http://www.developerdotstar.com

Steven’s picture

If you need a printer-friendly site, implement printer stylesheets. They are used automatically by any browser.

Try doing a print preview on this page for example. The sidebar and header are not printed.

--
If you have a problem, please search before posting a question.

pamphile’s picture

From a search engin stand point. I've been wondering if Print pages would be seen as duplicate data. That would seriously hamper your status with the search engins.

Has anyone notices a drop in search engine traffic after implementing a printable version of their webpages ?

Marcel
Wholesale DIrectory
Business Letters
Free Classifieds

travischristopher’s picture

it provides a big page of content which google seems to prefer... i've found that doing google searches many times i'll find the printable version of the collabrative book content before i find the the actual site in the the search results. although the results very widely, depends on content size, keyword frequency and on site configuration.

Rick Cogley’s picture

... would be something like Ecto or wBloggar. This would at least allow you to save as you go to your local drive (call me paranoid), but still post within the Drupal framework to give you the integrated searching and use of taxonomy. However, I am not sure if the blogapi allows posting to anything other than blogs.

That said, you can probably edit your wysywig editor settings so the width of the htmlarea you're using is wider and more easy to use and see, and, enable advanced features to make editors' lives easier. Still need to think this through more...

Rick Cogley :: rick.cogley@esolia.co.jp
Tokyo, Japan

sepeck’s picture

I believe that the blogapi allows you to post to other content types than blog.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

incidentist’s picture

I run the site for a think-tank that publishes articles and reports on its site. We use Plone for the articles and CivicSpace for our forums and other "interactive" stuff. Drupal could do pretty much everything you'd need to do on an article-driven site except for one important thing: paginated articles. That's a must. (Yes, I'd be interested helping with development of this, as I've just started hacking Drupal.)

--
Dan Kurtz - http://www.brickswithoutclay.com
The Rockridge Institute - http://www.rockridgeinstitute.org

venkat-rk’s picture

You are spot on. There are some efforts to do this with flexinode, but I forget the forum postings relating to that.

But, I also think that you can create paginated articles by first building the articles with the book module and then playing around with the theming to paginate them.

Edit: I just found this thread that may offer a possible solution to pagination through theming.
http://drupal.org/node/10937

Prometheus6’s picture

Drupal could do pretty much everything you'd need to do on an article-driven site except for one important thing: paginated articles.

Piece of cake.
http://www.niggerati.net/node/215

I've seen the request enough now that I'm considering one of those reverse bounty things, maybe $100.

venkat-rk’s picture

That's a nice site. Lovely use of colour (at least for me). And, its obvious that you can paginate pages.

Please consider donating your innovations back to drupal by getting a CVS account.

Prometheus6’s picture

Actually, I have one. Check my profile to see the modules I've contributed.

It is my position that I have to return something to the project because I am damn sure not going to write a core system of Drupal's quality.

Prometheus6’s picture

I looked around at some other reverse bounty things. I thought it was a collective thing rather than one person commissioning a module.

$100 is more than I'd be willing to pay as an individual.

I need to think about this.

venkat-rk’s picture

Sorry, I now remember having seen your profile before. Somehow escaped me when I was posting.

As you mentioned, $100 is more than one individual can afford, but at the same time, it should be your own decision to contribute or not. Nice work though, all your modules do interesting stuff.

Prometheus6’s picture

Yeah, I misunderstood the reverse bounty because I thought is was a community thing. I deal with individuals way different than I do funded organizations, especially if I like what they're doing.

dcc1225’s picture

Prometheus6,

I've looked at the site and the source for this--cool. Are you willing to share how you did this? Is it a custom module with automatic pagination, or did you name each page using pageno=x?

<a href="/node/215?pageno=4" class="active">
Prometheus6’s picture

It's a custom module with two functions (the hook_help() function doesn't count): one to build the page links and a hook_nodeapi() implementation that kicks in when you view a page. It splits the node into pages (explode()) on each <!--pagebreak--> comment it finds unless you ask for pageno=ALL.

incidentist’s picture

You make it sound so easy!

I'd love to see this get into the core distribution.

--
Dan Kurtz - http://www.brickswithoutclay.com
The Rockridge Institute - http://www.rockridgeinstitute.org

kitt’s picture

Using Prometheus6's suggestions, a pagination module:

http://kitt.hodsden.com/pagination.module.gz

Download, copy to your modules directory, enable it via your admin/modules page, adjust the text for your "Go to page:" "Next" "Previous" and "One Page" links via the settings page (admin/settings/pagination).

To enable paging in a page add, an HTML comment with "pagebreak" in the comment:

The full page will break on the pagebreak comments and display the page links at the bottom of the page.

Let me know if you'd like something different.

robertdouglass’s picture

Kitt,

do you realize that by releasing this under a Creative Commons license you preclude it ever being included in the drupal.org repository? Might you consider re-releasing under GPL?

- Robert Douglass

-----
If this helped you, please take the time to rate the value of this post: http://rate.affero.net/robertDouglass/

www.hornroller.com, www.robshouse.net

robertdouglass’s picture

I think you can replace the manually constructed links with a theme call:

$links .= ' | ' . l($x, $basepage, array(), 'pageNo=' . $next . ' ');

becomes

$links[] = l($x, $basepage, array(), 'pageNo=' . $next . ' ');

theme('links', $links); // $delimiter is '|' by default

- Robert Douglass

-----
If this helped you, please take the time to rate the value of this post: http://rate.affero.net/robertDouglass/

www.hornroller.com, www.robshouse.net

robertdouglass’s picture

Your use of

$x = variable_get('pagination_prev', 'previous');

is dangerous, since these variables are site-wide globals. What you need is something specific to the session (like $_SESSION) or another GET parameter. I think adding these to the URL is the best bet.

- Robert Douglass

-----
If this helped you, please take the time to rate the value of this post: http://rate.affero.net/robertDouglass/

www.hornroller.com, www.robshouse.net

kitt’s picture

1. There are no instances of pagination_* anywhere in the Drupal codebase to conflict with this module's use of them.

2. I *do* want pagination_* to be site-wide. How else would you store configuration variables? I don't want the user to have to edit the module directly to modify the text.

The pagination_* variables refer to the text that is displayed on every page that uses this module (for example, I might want the text "View all" You might want "Single Page"). Allowing the user to configure the variables is nice, since I have no idea what text you want to use.

3. Or are you refering to the use of $x? If so, I would also question that it is dangerous. It's a local variable.

4. If you think pagination_previous refers to the previous page number, please review the code.

robertdouglass’s picture

Scratch my last comment, I misread the code. I do think, however, that a simple t() would be better. That more readily gives people control over the text that gets used (through the locale module) and allows for different languages.

- Robert Douglass

-----
If this helped you, please take the time to rate the value of this post: http://rate.affero.net/robertDouglass/

www.hornroller.com, www.robshouse.net

robertdouglass’s picture

Heres a suggestion for how you could use hook_link for the pagination links instead of tacking them onto the end of the content:

/**
 * hook link.
 * Sice this gets called after nodeapi we can use nodeapi to build $links and store it statically
 */
function pagination_link($type, $node = NULL, $teaser = FALSE) { 
  // dummy variable
  $var = null;
  return pagination_nodeapi($var, 'links');
}


/**
 * nodeapi hook
 */
function pagination_nodeapi(&$node, $op, $teaser = NULL, $page = NULL) {
  static $links;
	
  // return statically stored links to pagination_link
  if ($op == 'links') {
    return $links;
  }
	
	
  switch ($op) {

  case 'view':

	  if ($page === true) {
		  
		  // explode the body on the <!--pagebreak--> tag
		  $pages = explode('<!--pagebreak-->', $node->body);
		  
		  // if more than one page, generate the links on the bottom
		  if (count($pages) > 1) {
			  
			  // process only if the user doesn't want all the pages
			  $pageNo = $_GET['pageNo'];
			  
			  $totalPages = count($pages);
			  
			  // check we're not too far or too few
			  if (!isset($pageNo) || empty($pageNo)) {
				  $pageNo = 1;
			  }
			  
			  if ($pageNo > $totalPages) {
				  $pageNo = $totalPages;
			  }
			  
			  if ($pageNo != 'ALL') {
				  
				  $basepage = $_GET['q'];
				  
				  for($i = 1; $i <= $totalPages; $i++) {
					  if ($pageNo != $i) {
						  $links[] = l($i, $basepage, array(), 'pageNo=' . $i);
					  } else {
						  $links[] = $i;
					  }
				  }
				  
				  $prev = (($pageNo - 1) < 1) ? 1 : ($pageNo - 1);
				  $next = (($pageNo + 1) > $totalPages) ? $totalPages : ($pageNo + 1);
				  
				  if ($pageNo > 1) {
					  $x = variable_get('pagination_prev', 'previous');
					  if ($x != '') {
						  $links[] = l($x, $basepage, array(), 'pageNo=' . $prev . ' ');
					  }
				  }
				  
				  if ($pageNo < $totalPages) {
					  $x = variable_get('pagination_next', 'next');
					  if ($x != '') {
						  $links[] = l($x, $basepage, array(), 'pageNo=' . $next . ' ');
					  }
				  }
				  
				  $links[] = l(variable_get('pagination_single', 'Single page'), $basepage, array(), 'pageNo=ALL' . ' ');
				  
				  $node->body = $pages[($pageNo - 1)] . '<p />';
				  
			  } // end check for ALL param
			  
		  } // end check for > 1 page to display
		  
	  } // end check if we're on a page
	  
	  break;
	  
  } // end switch
} 

- Robert Douglass

-----
If this helped you, please take the time to rate the value of this post: http://rate.affero.net/robertDouglass/

www.hornroller.com, www.robshouse.net

kitt’s picture

Um... that'll call nodeapi twice: once when the module's nodeapi function is called when a node is viewed, then again when the links function is called.

Pretty sure that's not what I want.

robertdouglass’s picture

Nodeapi gets called sometimes 7 or 8 times for some page loads. If you can find a different way to put the links in the traditional links region that would be fine. Of course you can just leave your module as it is - I'm not criticizing it. I'm just making suggestions for what I see as improvements.

Anyway, I don't think the overhead in my suggestion is a concern, though I do agree that the methodology is a little 'dirty' and a cleaner solution would be desired. The problem is, one basically has to do the pagination logic in nodeapi or some other early function and by the time it gets to hook_link the links would already have to be built, so some mechanism for storing the array until then has to be thought of. The solution of using a static variable and calling nodeapi with a specialized $op doesn't seem like the worst way to do it. A global $links would be much dirtier in my opinion.

- Robert Douglass

-----
If this helped you, please take the time to rate the value of this post: http://rate.affero.net/robertDouglass/

www.hornroller.com, www.robshouse.net

Prometheus6’s picture

The problem with putting the pagenation links in the traditional area will become obvious once you have enough pages.

robertdouglass’s picture

This would apply to the normal content area too, though, albeit with more available real estate to start with. I guess one needs to decide how it's going to be used on a particular site. I don't suppose anybody would choose to make a 30 page post with this method when we have the book module available.

- Robert Douglass

-----
If this helped you, please take the time to rate the value of this post: http://rate.affero.net/robertDouglass/

www.hornroller.com, www.robshouse.net

noid’s picture

Does this work for all node types? Tried the module, but it doesn't seem to be working. Should I add something in the allowed html tags configuration? Thanks.

Am using 4.6.1

kitt’s picture

It should work on all node types. If you have requests or questions, you can email me via the user contact page. I'm happy to make improvements.

Tim_Olaguna’s picture

Well, I still can't get long articles (in this case, a story) to break as requested on my PC test site. A two and a half page story still comes out as one long piece. The only way I have been able to break up a long piece is to tediously set up child pages individually using the Book content option and copy and paste each page portion from my PC-based Word document into each child page. A not-at-all efficient approach.

What editor is this module proven to have worked with? The newest Fckeditor? TinyMCE? HTMLarea? None?

What input format is suggested? Filtered HTML? Full HTML? A customized Rich-text editing format?

If I can't resolve this pagination issue easily I will have to abandon Drupal as a not yet ready CMS for my needs.

Cheerily Yours,
Tim O'Laguna

Former Commodore 64 Junior Wizard

Tim_Olaguna’s picture

Would someone please respond to the above issues and questions?

Thank you..

Cheerily Yours,
Tim O'Laguna

Former Commodore 64 Junior Wizard

noid’s picture

It only works with Full HTML. Here's why it doesn't work with Filtered HTML -- http://drupal.org/node/25346 .

Tim_Olaguna’s picture

Thank you for explaining. That makes sense.

But that also means this whole module is not an appropriate choice for my non-technical HTML-uninformed (or even interested) writers and story tellers. Either that or I would have to review, edit, and reformat all of their submissions. Not an acceptable alternative. It appears Drupal is simply not developed enough to meet my needs.

I guess I'll need to take another look at Mambo/Joomla; even though their defaut What's-popular what's-hot what's-not what's-the-latest-news quick-take-a-poll airhead approach to CMS presentation makes me ill.

Mutter, mutter, mutter. Not so ...

Cheerily Yours,
Tim O'Laguna

Former Commodore 64 Junior Wizard

noid’s picture

Hi kitt,

The pagination module needs to be modified so that it works well with printer friendly pages, also known as the print module.

That is,

node/id should be the Single Page, so that node/id/print should display the print view of Single Page. (This will work whatever page number you are viewing, since the "printer friendly version" link always point to node/id/print.)

With the current code however, node/id refers to page 1. Thus, node/id/print always displays the print view of the first page only.

Thanks for a great job! :)

venkat-rk’s picture

There are two print friendly pages modules. I assume you are referring to this?
http://drupal.org/project/print

noid’s picture

Yes, ramdak. Didn't notice the other one before. Viewed it and there's no download link -- http://drupal.org/node/8240 .

kitt’s picture

I made the following changes.

1. Licensed under the GPL. Have at it, folks.

2. Added a "break pattern" setting so that the module can work with Filtered HTML nodes. The default is "<!--pagebreak-->" but you can now set up a different pattern in the settings page (admin -> settings -> pagination). Set the pagebreak pattern to something your "Filter HTML" input will allow, recalling the content will display when showing the full page (say, for printing).

A good workaround would be adding <pagebreak> to allowed HTML tags, and using it as the pagebreak setting. It won't be valid HTML on the full page, but the tag won't render, either.

3. Will now display the whole page with "node/#/print" URLs, as well as "&print" URLs (which, say, the civicspace themes from factoryjoe use).

As for other comments made, I have a CVS account, been waiting for a reset on my password to add the module to the repository.

Will probably not add the feature to display the links if a single page is displayed.

venkat-rk’s picture

Thanks, Kitt, especially for the GPL.

Is the updated module available at
http://kitt.hodsden.com/pagination.module.gz

kitt’s picture

Works with 4.6. Haven't tested with any other version yet.

You know, the CC license is very generous. I'm unsure why everyone was in a tizzy about it. I just said you couldn't sell it and had to keep my name and the reference to Prometheus6 in the comments.

Anyone care to enlighten me?

handelaar’s picture

Everything in Drupal repositories is GPL.

GPL requires that your copyright is respected.

GPL requires that if anyone modifies and redistributes your stuff they have to acknowledge your copyright.

GPL puts no restriction at all on selling, provided the first two conditions are met.

Your CC license is more restrictive, therefore. I won't say it's worse, because your license is your own choice. Just that I won't be using your code in any client site because your license forbids me from doing so (such work would certainly not be 'noncommercial') and compared to the hundreds of other modules in contrib, I certainly don't agree that your license is 'generous'.

venkat-rk’s picture

Well, Kitt responded to the request for GPL a long time back.
http://drupal.org/node/23362#comment-61397

May be you were just explaining?

noid’s picture

Thanks kitt for your efforts and generosity! They are well-appreciated. :)

I've tested the module and here are my observations:

1. All pages now work with the print module perfectly. We get the print version of the entire article each time the printer friendly version link is clicked in any of the pages. :)

However,

2. I have the tinyMCE editor installed, and when it is enabled in a particular textarea, both the <!--pagebreak> and <pagebreak> tags don't work. When you disable tinyMCE in the particular textarea, you'll see that the tags are converted to &lt;!--pagebreak--&gt; and &lt;pagebreak&gt; respectively. 

a. If you disable tinyMCE or rich text editing, and convert &lt;!--pagebreak--&gt; to <!--pagebreak> (and set filter to Full HTML), the pagination works; also when at the outset you disable tinyMCE and place <!--pagebreak>, pagination works.

b. In the beginning, I was able to make pagination work by converting &lt;pagebreak&gt; to <pagebreak>; however, later, when I tried again, I couldn't duplicate my success. And even when I was successful, when I tried editing the particular node again, the <pagebreak> tags disappeared, and thus I have to put in the <pagebreak> tags again.

At any rate, in both instances, what is needed is for the pagination module to work with TinyMCE (or any editor for that matter?) -- that is, the module should be able to retain the <!--pagebreak> and <pagebreak> tags even with TinyMCE on; in other words not to let TinyMCE convert the < >'s.

Perhaps a <!--pagebreak> and <pagebreak> filter is needed? Much like the adsense filter in the adsense module -- [adsense:format:group:channel]? (The adsense tag works even with TinyMCE enabled). Anyway, that's just an idea and you're the  expert. :) Keep up the great job! :)

P.S. Sorry I had to use the code tags for the most part of the post -- had to escape the <>'s. :)

tostinni’s picture

You should see with the TinyMCE maintainer to add this tag to their tag list (or at least know how to add this in order to keep the > and < well formated.

venkat-rk’s picture

Hello Kitt,

Great work on this module!

I realise you are doing this as voluntary work, but it would be doubly great if you could find time to implement noid's latest suggestions on making this work with printer friendly pages.

Also, please, please consider applying for a CVS account on drupal and releasing this under GPL. It seems to be too good a module to be lost to drupal because of the CC license, although you probably had your reasons for doing that.

Thanks once again,
Ramdak

noid’s picture

I was also thinking how this module could be implemented so that it will work with Filtered HTML, and thus regular users can also use it. Otherwise you can't enable Full HTML for regular users since it's a security risk (correct me if I'm wrong).

noid’s picture

Also noticed that when you click Single Page, the links to other pages disappears. The links should be retained so the user can navigate to specific pages if the user wants to.

m3avrck’s picture

Any chance of getting this module as a real contrib module on CVS? Seems like it would be really useful instead of just buried in this thread :-)

iandickson’s picture

I'm doing something similar.

1) Essentially in my site I'm using Flexinode to create several Content Types to meet each kind of formally structured entry.

Where required, special Vocabs are assigned.

2) In some cases subadmins will gather posts into Books.

E.g a local history group might contribute articles, and their editor arranges them in a book.

Eventually the whole thing probably gets edited into a coherent BOOK about local history.

(Coherent books don't just happen, even though the raw content might).

3) I am also playing with extra Input Types and filters- for example you can allow inline images by changing the HTML filter - though I haven't yet moved that to the public area.

4) The taxonomy question is key - it does get complex. The trick is to try an tie vocabs to 1-2 CTs, and then write Search pages that show the user a context based subset of taxonomies, which then generates a taxonomy URL to get the content.

So when they are in Film, they might choose between Genre and Region to find "A comedy in their local town". When in Property, it's Bedrooms, Type, Location, Min Price, Max Price.

So doing articles out of the box is maybe hard, but with careful thought re structure, and some PHP to help users zoom in on the right stuff, certainly possible.

Prometheus6’s picture

(Coherent books don't just happen, even though the raw content might).

True. You will find that your next/previous page links navigate in node id order reather than as weighted...the weight only affects the order the links to each page shows up in the book navigation block.

I just noticed that yesterday >:-|

pamphile’s picture

The pagination module is awesome ! It adds a great level of usefulness.

My problem with the Book module is that is that the pull down feature during edit causes trouble when your got thousands or tens of thousands of book pages.

YP.BZ - Yellow Page Dot Business
Advertising Blog and Diary
Internet Domain Blog

Prometheus6’s picture

Agreed. In fact, I submitted a patch that won't make it to core because it requires Javascript.

http://drupal.org/node/27736

You get two combo boxes: select a book and the second updates with ONLY the pages of that book. Huge improvement, if I do say so myself.

agentrickard’s picture

I like the pagination.module as proof of concept. But has anyone done auto-pagination similar to the teaser settings in Drupal core?

That is, instead of definining a page break tag, I'd like to define a character limit at which page breaks will be written automatically.

Feasible? Implemented?

Please share.

--
http://ken.blufftontoday.com/

noid’s picture

That's a great idea. :) I'm just a beginning programmer of Drupal so can't really comment how feasible this is, but hope somebody does try to implement it. :)

agentrickard’s picture

It's feasible, but my code skills aren't good enough to get it done. :-(
--
http://ken.blufftontoday.com/

Zethris1’s picture

I'm working on that.

Since the dev of this module seems mia, I have been having to make changes I needed on it on my own, and I am now working on an auto-pagination feature to it that counts characters, words, and paragraphs and you can set any of them to auto page to the next and also set it to look for a subtopic/chapter header (looks for bold html calls) to call the "Next" link something more interesting than just plain "Next" or "Previous"

I will probably have to rewrite so that I can release a CVS project of it. So i'll keep you posted.

Visit http://www.thinkingpost.net to add your thoughts and ideas to the community.

noid’s picture

Hey Zethris1,

That's great! Thanks for your time and effort. Looking forward to your module. :)

kitt’s picture

Just waiting for my CVS access, which I've just received an email about. Whoo!

bharanikumariyerphp’s picture

Hi dear,

am also in the same boat,

What u faced once upon time, now am facing that problem,

Can u tell me simplest solution for ur problem, or send the code for the problem,

Plz dont recommend the pagination