| 1 |
*******************************************************
|
| 2 |
README.txt for nodeorder.module for Drupal
|
| 3 |
*******************************************************
|
| 4 |
The nodeorder module gives users an easy way to order nodes within their
|
| 5 |
taxonomy terms.
|
| 6 |
|
| 7 |
By default, the taxonomy module orders listings of nodes by stickiness and
|
| 8 |
then by node creation date -- most recently posted nodes come first.
|
| 9 |
|
| 10 |
The nodeorder module gives the user the ability to put nodes in any order they
|
| 11 |
wish within each category that the node lives.
|
| 12 |
|
| 13 |
There are two ways that a user can order nodes within a category. The first
|
| 14 |
is to use the "move up" and "move down" links that can be configured to appear
|
| 15 |
on each node (especially useful when looking at lists of taxonomy terms). The
|
| 16 |
second is to use drag and drop, which appears on the administrative listings
|
| 17 |
of nodes in a category.
|
| 18 |
|
| 19 |
To install the nodeorder module:
|
| 20 |
|
| 21 |
- Put the nodeorder directory in your modules directory.
|
| 22 |
- Navigate to administer --> modules, and enable the nodeorder module.
|
| 23 |
- Navigate to administer --> access control, and assign one or more roles
|
| 24 |
the right to "order nodes within categories."
|
| 25 |
- You may turn on "orderability" on a per-vocabulary basis by visiting your
|
| 26 |
vocabularies' administration pages (admin/taxonomy). This module adds a
|
| 27 |
checkbox on the "edit vocabulary" page titled "Orderable" -- it defaults to
|
| 28 |
being unchecked. After checking this box and saving your changes, you'll be
|
| 29 |
able to order nodes that are classified in this category.
|
| 30 |
|
| 31 |
- To use drag and drop node ordering, you will find a tab called "order
|
| 32 |
nodes" on any admin/taxonomy/VID pages where the vocabulary has been set to
|
| 33 |
orderable.
|
| 34 |
|
| 35 |
- Navigate to admin/settings/nodeorder, where you can set some options
|
| 36 |
that determine the way nodeorder works.
|
| 37 |
|
| 38 |
TECHNICAL NOTES:
|
| 39 |
|
| 40 |
Upon installation, this module adds a new column (weight_in_tid) to the
|
| 41 |
term_node table. Adding a column to a core table? Are you crazy? Yeah,
|
| 42 |
I guess so ... but it lets us keep the module's code very small since
|
| 43 |
most everything works through taxonomy. Also it helps to avoid an extra
|
| 44 |
join for every node listing.
|
| 45 |
|
| 46 |
Please note that the node order is only respected when visiting links
|
| 47 |
that begin with "nodeorder" -- if you visit links that begin with
|
| 48 |
"taxonomy" they will appear in the generic taxonomy order. Since the
|
| 49 |
module implements hook_term_path, the taxonomy links that get printed
|
| 50 |
per node will correctly point to the "nodeorder" space when they are in
|
| 51 |
orderable vocabularies.
|
| 52 |
|
| 53 |
The nodeorder module was developed by FunnyMonkey.
|