Last updated September 23, 2011. Created by NancyDru on March 11, 2009.
Edited by rcross, btopro, heather, joachim. Log in to edit this page.
Comparison of Node Ordering Modules
The standard ordering for lists of nodes in Drupal is first by the "sticky" attribute and then by the created date. Many content modules have some facility to change this ordering, but only for their content type. The modules described here attempt to provide a more controllable ordering in a variety of ways.
| Feature | Outline Designer usage |
Weight usage |
Nodeorder usage |
Nodequeue usage |
DraggableViews usage |
Flag Weights usage |
|||
|---|---|---|---|---|---|---|---|---|---|
| Drupal-related | |||||||||
| Drupal 7.x | planned |  |
dev | Beta released | dev | ||||
| Drupal 6.x | |
|
|
|
|
|
|||
| Drupal 5.x | |
|
|
|
 |
|
|||
| Drupal 4.7.x | |
|
|
|
|
|
|||
| Last official release | 2010-Oct-27 | 2011-Sep-21 | 2009-Nov-15 | 2009-Nov-05 | 2010-Feb-07 | 2008-Oct-10 | |||
| Documentation | Handbook README.txt |
Handbook README.txt |
README.txt | Handbook README.txt |
Handbook README.txt |
Handbook README.txt |
|||
| Demonstration | Demo | No | No | No | Demo | No | |||
| Architecture | Upgrades Book outline interface | Sticky-encoding | Adds a field to term_node table | Views style plugin | Add-on to Flags module | ||||
| Additional database tables | 0 - purely usability / functionality upgrade | 0 - uses node table's sticky column | 0 - adds a field to term_node table | Yes | 2 by default | 0 - adds to flag module table | |||
| Services provided | |||||||||
| Reordering page | Drag and drop, duplication of book outlines, AJAX version of book module, context menu | Uses core node admin page | Drag and drop | Drag and Drop interface for D6, Custom Javascript interface for D5 | Any view | API only, or see integrating with draggable views | |||
| Feature blocks | Inherited from book module | N/A | None | Inherited from views | None | ||||
| Supports Managing Translated Nodes | Yes, either by tying translations to the original or by ignoring translations and letting admins manage them as separate nodes | ||||||||
| Security | Drupal core-optional books module | Drupal core, 'assign node weight', 'administer nodes', 'administer site configuration' | Drupal core | Separates permissions for ordering nodes from editing them | Views permission, plus 'Allow Reordering' | ||||
| Settings | Yes | Yes | Yes | Yes | Yes | N/A | |||
| Views support | |
|
|
|
|
|
|||
| Translation template supplied | |
|
|
|
|
N/A | |||
Outline Designer
The Outline Designer is an enhancement to the core-optional books module packaged with Drupal. It provides a drastically improved UI as well as additional functionality that can help books be a more attractive, simple option then fully configuring other projects. This in use with projects like Menu Block can help you structure site outlines and node hierarchies rapidly. This project has been created as part of the ELMS initiative. Read more about the module here: Outline Designer
Weight Design
The Weight module uses the "sticky" attribute by altering its value to include the node's weight. This has the advantage of making the standard node ordering automatic with no further changes. The disadvantage is that modules that check the sticky attribute for 0 or 1 (FALSE or TRUE) may not work properly, although the module will decode the two values upon a full node load.
Nodeorder Design
Using taxonomy, individual nodes can be classified multiple ways. See
Taxonomy: A way to organize content for a comprehensive description. To continue the analogy from there, Nodeorder allows you to say that "this node should appear towards the top of the list of composers but towards the bottom of the list of seventeenth century."
Upon installation, Nodeorder adds a column called weight_in_tid to the term_node table. On each Vocabulary's edit page, Nodeorder adds an "Orderable" checkbox. If this is checked, users with the correct permissions will be able to order nodes within any of the terms in that vocabulary.
Nodequeue Design
Provides a simple UI to manually order any queue. Additionally, it allows nodes to be added and removed from queues without needing edit permissions to the node. Nodes can be added to queues either from a queue management tab or by links on the node teaser. Nodequeue provides a robust Smartqueue API so module developers can create customized queues that are specific to particular users, or to Organic Groups.
For more info please see the Nodequeue project page
DraggableViews Design
Rows of a view can be moved via drag-and-drop to build hierarchical structures. Child nodes of parents can be hidden via javascript. Paging is fully supported since rows can be dragged from one page to another.
The default implementation uses a database table to save the information. Additional handlers can be implemented to save the information elsewhere. Currently there are two additional implementations: CCK-Handler and Flag-Weights-Handler.
Flag Weights Design
Flag Weights module is an add-on to the excellent Flag module, that adds the ability to set a weight against each flagged item. The module does not provide any UI as such, other than integrating with Draggable Views module to allow drag'n'drop reordering or flagged content. This might be used for prioritising a wishlist, etc.
Comments
Sort by taxonomy vocabulary?
Looks like none of these sort nodes by taxonomy vocabulary's natural ordering or weight? Am I reading correctly?
No
You may be missing the point here. These modules are to allow you to control the order in which nodes are presented rather than an arbitrary Drupal way. But actually, I know of no module that presents nodes according to Taxonomy except maybe Taxonomy List.
[Edited by kiamlaluno to fix the tag IMG]
NancyDru
Oops, did you mean to stop
Oops, did you mean to stop typing at "maybe"? :-)
Oops
Taxonomy List
NancyDru
*cough*views*cough* :D
*cough*views*cough*
:D
Views cannot natively do what
Views cannot natively do what I asked about above.
Well, I wasn't answering your
Well, I wasn't answering your question, but now I will: the default sort for taxonomy (and the front page) is just by date/time. Views also sorts this way by default. If that's not what you mean, you need to make your question clearer.
If you visit a taxonomy,
If you visit a taxonomy, you'll see the terms in a particular order. I'd like to have nodes display in that same order.
That order is Date,
That order is Date, Descending (newest first), exactly the same as views. Look: http://drupal.org/taxonomy/term/1766
If you visit
admin/content/taxonomy/taxonomyId shows terms sorted by weight. That's what I'm talking about--how to display nodes but using their respective taxonomy items' weight for primary sort.
Yes
Taxonomy List can do that.
NancyDru
Reopened #283558: Views
Reopened #283558: Views integration to get more info.
Confusing!
Ahh, confusing. Your first question was about NODES (what this page is about), then it morphed into TERMS. They are two very different things. You CAN sort taxonomy terms by weight.
Go to admin/build/views/add and select "term", then in the new view, add the field "Taxonomy: Term" and any other fields. The default sort is "weight", and you can change it in "Sort" by adding the "Taxonomy: Weight" field. You can also sort nodes by "Taxonomy: Weight" in much the same way.
No
He wants the nodes listed in the order of the terms.
* Term 1
* Node 101
* Node 102
* Term 2
* Node 203
* Node 204
etc.
NancyDru
Practical example for its main page
Suggestion: That is a practical example to place on the Taxonomy_list main page.
Book module?
Thank you for this page. However, I'm not clear on why the core Book module is not included in this comparison.
Because
A) it is not a contrib.
B) it is not a more general purpose node ordering feature.
However, if you feel strongly about it, join the Doc team and add it to the page.
NancyDru
Thanks, Nancy, but if I knew
Thanks, Nancy, but if I knew enough about this issue to be on the doc team, I wouldn't be looking for an answer to this question, because I'd already know the answer. :-) I'm asking the question, not because I want to contribute the answer, but rather because I came here looking for the answer.
I came to this page to find out how various node-ordering modules compare to the Book module, which I'm already using and understand. I am not using and do not understand the other modules you're describing in this page. The page helps me to understand how they differ from each other, but not how they differ from the Book module. The page also doesn't say it is limited to contrib modules, nor what is meant by a "more general purpose node ordering feature." More general purpose than what? The Book module? Or something else? I'm confused.
Thanks again.
Yes
Yes, more general purpose than Book. Right now, RealLife™ is screaming at me, so I don't have the time to devote to adding Book here (frankly, it was an oversight when this was started because not that many people use Book).
The only one here that I personally am responsible for is Weight, which I took over some time ago. It is a relatively simple module that adds weighting (similar to Book) to any node. It does so by encoding the weight into the Sticky field so that standard Drupal queries should work without any "fiddling." It's not perfect because some modules don't do "standard" queries, and some actually look at the sticky field and get confused. But those are few, and easily fixed when identified.
NancyDru
nodeorder sent my site offline
If you add any query you have a join no server can stand!
şarkı sözleri
Popularity
As of 3/8/2010, module popularity per http://drupal.org/project/usage is:
I think this should be in the table above.
Feel free
Feel free to update the table.
NancyDru
I can't. There's no Edit tab.
I can't. There's no Edit tab.
Hmm...
I assume you are logged in. Since this node contains a table, you probably need to join the documentation team, which is no big deal and does not commit you to any further updates.
NancyDru
Nodequeue is much more popular
Nodequeue is much more popular than that. The current number is 8,819 and has not been below 1000 all year. I don't know where you got 123 from ...
One thing I absolutely LOVE about nodequeue is the smartqueue functionality. This will automatically create a new queue to manage the sorting associated with taxonomy terms, users, organic groups, etc. This, to my knowledge, can not be achieved with any other sorting module.
The nodequeue admin page gives drag and drop sorting, but I do wish that draggable views was able to integrate with nodequeue to provide more user friendly sorting administration.
Michael Thorne
Rank
123 is Nodequeue's rank in the module popularity list, not # of users. It has increased a hair since I last checked.
Please update Last official
Please update Last official release
And add usege statistic
Join
Join the docs team and update it all you want.
NancyDru
I wanted to add usage stats
I wanted to add usage stats to the table, so I tried to join the docs team, but ran out of time just learning how to join the docs team. Here's a summary of what I found so the next person can jump right in (this info accurate as of 2010_07_12).
http://drupal.org/contribute/documentation/join
"You need not apply to be a part of the documentation team. Once you edit or create new pages using the "add child page" link in the handbook, then you're part of the team. Go ahead and find a handbook page that you feel needs improvement or revamping and hit the big edit button at the top. "
http://drupal.org/handbook
So, once you edit a handbook page, you'll be able to edit other pages outside of the handbook. Within the handbook, there's a page about needed Documentation maintenance tasks.
http://drupal.org/node/302146
First item, "Incorporating comments"
http://drupal.org/node/135589
Right up there on that list is a list of all handbook pages that have comments:
http://drupal.org/handbook/comments
...including this very page. But I guess it's not part of the handbook so I can't edit. Loop!
This is where I ran out of time. Passing the baton...
Added links
There are now links to the usage stats in the table. Keeping that kind of information up-to-date will be a nightmare. Plus, by putting them there, you are encouraging people to use the most popular rather than the best for their situation.
NancyDru
In my drupal experience the
In my drupal experience the most used module is often the best choice if it suits your needs, which is probably why Drupal.org modules list is now by default ordered by usage. I think it would be useful to put the usage stats in the table even if they do get out of date, people will update them every now and then. Anyway this gives some idea order of magnitude style as of 30/09/2010 (I can't edit either):
Weight: ~3,000 (growing steadily)
Nodeorder: ~1,000 (growing steadily)
Nodequeue: ~10,000 (growing steadily)
DraggableViews: ~4,000 (growing fast)
Flag Weights: ~500 (not really growing)
I can't edit this page
I can't edit this page either. I think it is locked. I found some information about this here: Pages locked to editing.
Doc team
In order to edit a table, you have to have Doc Team privieges.
NancyDru
Drupal 7
Can we add a new Drupal 7 line to show support? Nodequeue has a development release out.
Nodequeue and Drupal 7
I've just downloaded Nodequeue 7.x-2.x-dev and installed in Drupal 7 alpha 7. Nodequeue doesn't work: "This version is not compatible with Drupal 7.x and should be replaced".
And...?
This is not the proper venue for support. Go to http://drupal.org/project/issues/noqequeue
NancyDru
Sortable Grid
I just released a module which somehow fits in this category : Sortable Grid
It's in early dev but I'm eager to obtain feedback from testers.
It's definitely not of the "all purpose" kind, but I think it can be useful in some use cases.
I must mention that I recently used Draggable Views on a D7 site which is now in production, so perhaps an update of the table above would be fair.
Error in D7 support
It seems as though one needs to be `Documentation Admin` in order to edit this page. Please update the D7 support row. I list *changes only* here.
Weight, flag weights and Node Queue have dev versions
node_order does not.