Please help us with taxonomy node pagination
Hi all!
Greetings.
We have approximately 20,000 pieces of articles, literary item etc.
We will like to move this onto drupal and after that more will be kept on adding by the users.
After exploring, found that the taxonomy module and nodeorder is helping us a lot
but there are certain bottlenecks it seems so far as paginated content is concerned.
As an example let us assume
we have a taxonomy term "flowers"
Under "flowers"
there are nodes like
roses
dahlia
poppy
lotus
By using nodeorder
we make this in any order wanted
lotus
poppy
dahlia
roses
Now when we see the taxonomy/term/6 page
we see ( considering we have set pagination at per page)
lotus
poppy
[ page 1 2 ]
When an user click on lotus, he gets the node page lotus with details
What we want here is
lotus
blah blah
blah blah
[ << prev 1 2 .... 4 next >> ] <--------- this pagination is not for the list
but to directly access the nodes 1, 2, 3, 4 the numbers 1,2 being in the same order as determined by the nodeorder.
It is similar to popular acidfree gallery script where if you click on the title in a list you are taken to a page that displays the node with pagination links [1 2 3 4 ] for all the nodes within the same category.
Here what is needed is pagination and that will respect the nodeorder.
Downloaded many of the taxonomy related modules but may have missed the one that can do the above.
Any tips page or any module, if known to you, can help us immensely.
=-=
have you looked into the paganation.module or custompagers.module?
Edit: I see you tried the custom_pagers.module based on your issue there.
More on this
All these modules work for the title list pages or the teaser list pages.
Consider the book module, where you have topics like
rose
apple
orange
jelly
Now when you visit the node page "apple"
you have links at bottom like
< rose .......... orange>
What I want is
< rose 1 2 3 4 ... orange>
This is very logical because when there are lots of pages it makes navigation direct instead of having to go through the next-prev links or hitting the "up" or list page.
When you drag and reorder bookpages the pagination above should also change
for example if page 2 opened "apple" it should then open "orange".
CMS is about handling content easily - I feel a little depressed that core coders have overlooked this.
=-=
Maybe it wasn't overlooked just unneeded at this time by anyone who can create work with pathes and issues and present patches to core issues.
I myself haven't played with pagers, matter of fact I don't know that I use them on any part of any sites I've built except for on the front page. Maybe I'll sit down with a brandy and a cigar tonight and see what I do with your idea and the custom_pagers.module after rereading the issue you placed in that issue queue.
edit some reasearch finds this: http://drupal.org/node/413868
which may be of help
If you do sit down with brandy and cigar
The link probably wont help but I had a cursory glance only.
If you do sit down with brandy and cigar and if you have working localhost please get a 6x copy of acidfree and enable book module also.
What happens after you set up a gallery, add some images and add these to book Outline and voila! you have superb pagination below each node, which gives BOTH "next" "prev" links and 1,2,3,4 ( referring to nodes and not list pages) AS WELL AS the title of the next and previous nodes. This is fantastic as acidfree nodes are basically image nodes which are themselves full-fledged nodes with work flow and all that, unlike other gallery modules.
So what is stopping me from using this pager ? The fact that people including the Acidfree developer refuses to mark the project green for no known reasons, and the other fact is that in Acidfree I am yet to find a way to place the image below the text. The second is not that important one.
=-=
I won't be installing acidfree, sorry. book has it's own pagers from what I've read acidfree in the mix is not something I feel like trying to work through, even if it was released as a stable version, I wouldn't require nor use that implementation for reasons already discussed.
Good luck
No problem, never mind.
No problem, never mind.
I just said to get illustration of this use case as there is no other way or module in drupal to achieve this.
=-=
I understand the illustration you presented.
But comparing Acidfree paging is likely problematic as it very well may be done in acidfree code because it is so self contained. Thus someone would need to open the acidfree module, work with teh paging system and see if it can be pulled out and put in the book.module. Which goes against you wanting to hack core.
If the above is the situation it explains further why I dislike self-contained modules that don't reuse drupal core or code from other modules and makes you completely dependant on it as a whole.
You are right
You are right.
I actually do not mean to hack but to "lift" the code and utilize it.
Acidfree does a hack actually and do not use the core or available code simply because the thing is not existent in any of these. For this same reason there are so many modules.
But then, are we getting anywhere ? I would be happy if my use case can be done in any other logical and core-ish way.
For this reason I posted this also http://drupal.org/node/498206 - a question for the core book module.
0 reply or 0 solution so far.
=-=
that may be a question for someone in IRC #drupal-support channel.
One must keep in mind that to answer support questions, one must have direct knowledge. When questions are so specific it will require the eyes of someone who has also done what you want to do. Thus you need someone who's worked with the book.module and someone who's altered it's paging system to be something other than what it is. I believe this is why the custom_pagers.module was created but as I don't use pagers, I didn't test that module very much. If I were to test again it would be with the -dev release as it's far newer than the last beta. The module was created by a well known contributor to drupal, so I'd trust testing the -dev on a test site.