This module gives you separate fields to describe names: prefix, first, middle, last, suffix. It gives you 'legal' and 'preferred' versions of these fields, and options of how to calculate a display name from the data. Sorts and filters are done by display name.

This module is experimental -- it does not yet support multiple values. It will be considered experimental until it does support multiple values.

Note: This module will soon be folded into the CCK Fullname module. We apologize for the temporary duplication.

A news module that uses Send to deliver one or more nodes to a mailing list.

Because News uses the send and MLM frameworks, it is short and efficient. But it includes all of Send's feature list, including CiviCRM integration, message history and HTML formatting. You can deliver news to any of MLM's mailing lists.

從 RSS aggregator 的分類裡，透過自訂關鍵字進行過濾，只讓含有該關鍵字的 RSS 項目，可以出現在這個新聞網頁上。例如我們可以在科技聯播分類裡收錄來自 Slashdot 和 Engadget 的文章，然後用 Taiwan、Acer、Benq 當作關鍵字，進行過濾，就可以自動製作出一個 台灣科技新聞 的頁面。

Allows creation of pages which show syndicated 'news' items from an aggregator category.

News items are automatically filtered by keywords (chosen when creating the page), so that only news items which contain a keyword are shown.

News pages can be placed in a book, and added to a taxonomy.

Adds a checkbox to site-wide contact forms allowing users to subscribe to your newsletter while contacting you.

The module notifies the administrator and includes the subscribe email address in the contact message.

It can also interact with a newsletter management system like Campaign Monitor (other systems can be added in one function).

Drupal 4.7 version now available via CVS. It's almost the same code as for Drupal 5.0

Future versions will include a settings page and support for more newsletter management applications.

輕易地製作出下拉式導覽選單，包括水平和垂直（選單向左拉或向右拉）兩種形式。

選單項目是從原本的選單而來的，你只要指定哪個選單要採用此模組所提供的功能，就可以達成此效果。

Nice Menus enables drop-down/right/left expandable menus for an unlimited number of menus. Uses CSS (and Javascript for IE).

Three styles/types of menus are currently possible: horizontal (menus drop down); vertical (menus drop to the left); vertical (menus drop to the right).

Menu items come out of the normal menu tree. Nice menus are blocks which can be placed wherever normal blocks can be placed. The module comes with a simple colour scheme which can be fully overriden with the user's normal stylesheet. Several CSS override examples are provided in the included README.txt file.

Current Roadmap

• The development version for 5 is available. THIS IS NOT READY FOR PRODUCTION USE! Only download this version if you are helping with testing and development.
• The 4.7 dev needs a number of fixes and general love before an official release is made but that is next on the list after 5 gets out the door. There will be no new features added to 4.7, only bug and security patches.
• 4.6 is now officially deprecated and will no longer be supported. The only patches or updates that will be applied are security patches.

Surely you have seen those cool rounded corners everywhere on the web these days. Even drupal.org uses them. The difference is that drupal.org uses corner images to achieve the effect.

With NiftyCube you can create those cool rounded corners without the need to make corner images. This means you spend less time in photoshop, the viewer is not punished if he has images disabled, change colors on-the-fly without the need to create new corner images, among other advantages.

This module makes use of the NiftyCube javascript found here. This module also has NiftyLayout for those who want/need it.

The Node Access Arbitrator is an experimental module API designed to allow multiple node access systems to work together.

Currently it is 4 modules

na_arbitrator

This is the core API module that all of the other modules depend on.

acl

This is a second API module (that probably should be folded into the arbitrator) that implements Access Control Lists. It requires na_arbitrator.

forum_access

A forum access control module that controls *only* access to forums. It includes role-based access as well as assigning individual users as forum moderators. It requires na_arbitrator, acl and forum.

workflow_access

A demo module that provides node access control to nodes based upon workflow state.

Because this module has been incorporated into Drupal 5.0, it will not need to be ported. I will continue to maintain it for 4.7, and I will hope that modules will be backported to 4.7 in order to utilize it.

Node Adoption provides one potential solution to the problem of node ownership when users are deleted. It allows admins to specify to whom ownership of orphaned nodes should be transferred when a user is deleted.

Sponsored by The Chicago Technology Cooperative

This module addresses a specific workflow for publishing nodes where nodes are to be created in published, unmoderated form, but approved by an administrator at a later time. It provides three extra tabs on the admin/node page; approved, disapproved, not yet moderated.

The controls on these three new pages allow you to approve, disapprove, edit or delete nodes.

Wishlist

The module does not yet do these things, which might be useful to some people:

• No new permissions are introduced. A user need the "administer nodes" perm to use these functions.
• There is no filter for node type, nor is there a setting that only some types are to be part of this system.

Maintainers

Robert Douglass
Mike O'Connor

This module allows those with the appropriate permissions the right to create blocks for each node. By default these blocks display the node title as the block title and the node teaser as the body. This can be themed by overriding the theme('nodeasblock', $node) function.

The NAT module is a helper module used to maintain node-term relationships, i.e. when a node is created, an equivalent taxonomy term is automatically created in any associated vocabularies. This module is a simple but effective way to create node-node relationships via the taxonomy module.

Testers, feature requests and patches welcome :)

Initially sponsored by: Moshe Weitzman.

This module create a new content type called node blaster. This can be added with title and description and more option becomes available on edit page where user can add node blaster content. This enables user to add series of content to be sent on a specified interval. User can select which day #node to be sent. This create a url that can be used for public.

This creates html form that can be used for signup. You can also add which url user will be redirected after signup. This code can be used on other site for signup process.

Node blaster mail is sent via cron jobs. Drupal cron jobs need to enable with 24h cycle.

This provides a feature to send site content (node) as an autoresponder.

TODO: Theming of node blaster email.

Allow you to customize menu location and breadcrumb of nodes depending on their content type, associated terms and others conditions.

Easily find any node with this module:

* List nodes by category
* List nodes by title
* List nodes by date
* Create a Node Tree (based on how nodes are categorized in the taxonomy)
* Uncategorized nodes (nodes not categorized in any taxonomy)

http://ftp.drupal.org/files/projects/node_browser-5.x-1.1.tar.gz
should work for all versions of Drupal 5.

The clone module allows users to make a copy of an existing item of site content (a node) and then edit that copy. The authorship is set to the current user, the menu and url aliases are reset, and the words "Clone of" are inserted into the title to remind you that you are not editing the original content.

Node Cloud reuses the popular "tag cloud" idea, but allows one to use nodes as the items in the cloud, instead of terms or tags. Node Cloud is a view plugin that presents the data returned from the view as a cloud of text, with the importance of each node indicated by the size of the text.

Node Cloud is fairly easy to use. To create a node cloud, go to your views administration pages, choose a view, and select "Node Cloud" in the drop down list of views plugins for either the page or block view. Choose two ordering criteria. Node cloud will do the rest.

Node Cloud tries to use some sane defaults to provide good out of the box support. Getting to know the default behavior will help you better understand what kinds of clouds you can create:

The order of the nodes in the cloud is controlled by the first sort order in the view. For example, you may wish to sort your node alphabetically or by creation date.

The size of the individual items in the cloud are controlled by the second sort order in the view. This sort should always be numerical. For example, you might size your nodes on how many votes each has received.

If you supply any fields, they will be displayed in the cloud. If you don't select any fields, a title link for each node will be used.

With this module comments can be full nodes. This opens the door for CCK types to be comments, for comments to have uploaded files, taxonomy, revisions, and anything else that comes from the goodness of nodeapi.

To use this module you need to first disable comment.module. The two are, and will remain, completely incompatible. If you don't disable comment module before enabling Node comments module, your site will crash.

This module is dependent on Views. Please have Views installed before attempting to use this module.

Once you have installed the Node comments module, you will need to create a content type to be your comments. This can be a simple type (provided by Drupal core), or a CCK type, or any other type. It is recommended that you call this type "comment". Whatever you call your type, you need to provide a node-yourtype.tpl.php file to your theme. One comes with the module; it is called node-comment.tpl.php. Move this to your theme directory, and if you ignored my advice and called your comment type something other than comment, rename the file accordingly.

Have fun designing interesting Views to render your comments. Your comments can now appear in tables, lists, or in any other view type that you can imagine.

This module allows users to either get notifications when a node hasn't been updated in x amount of time, to automatically unpublish such "expired" nodes, and/or to receive e-mail notifications and unpublish x days afterward.

Additional settings include allowing inheritance of the expiration settings from a book page to its children, renotifications (Notify user every x days before unpublishing), an email carbon copy address, and customizable email content.

In conjunction with book inheritance, an admin may decide who can and can't edit the expiration times while the parent book settings are still inherited.

If the admin sets the automatic unpublishing to anything but "Immediate", an additional page is available to view expired modules. ?q=admin/content/node/outdated

This module requires the use of Drupal's cron system for automatic unpublishing and email notification features.

With this module you can define relations between content types. It automatically creates a relation between all nodes, which have been created from the same user and have the defined content types.

It is a simple node relationship module, which doesn't provide any enduser interface. Relations are set automatically (based on admin defined content type relations) or programmatically through its API. It also allows to restrict the population of a content type (the number of creatable nodes of a content type per user).

The module doesn't display related nodes when viewing a node or anything similar. Currently it's up to the user to use the relation, e.g. use it to display related nodes during viewing a node (example provided) or use it for generating views in conjunction with views fusion

This module allows you to define any page or URL as the target, after you:

• create a node;
• update a node
• delete a node

It also has the option to send the target page a variable informing from where it came.
It works with nodes created with CCK.

Example of uses:

• Congratulations page.
• Guide the user on creating node after node
• etc...

Node History is a replacement for the revision list built into the node module.

With this module you can configure which columns are displayed in the revision list and how they are formated. A hook is provided for other modules to add columns or format rows and columns.

The columns provided by this module are the same as the built-in ones (vid, author, date, operations, log message).

可以從 CSV 檔案匯入資料到 Drupal 的某一內容類型裡（目前支援event/page/story/CCK/flexinode），並可設定內容欄位的對應方式。

通过CSV(Comma Separated Values)文件格式导入节点。

This module allows you to import a set of nodes from a Comma Seperated Values (CSV) or Tab Seperated Values (TSV) text file.

The module currently supports following types natively:

• event,
• page,
• story,
• any node type created with the Content Creation Kit (CCK),
• any flexinode node type.

Additionally it also has support for importing:

• event-enabled nodes,
• location-enabled nodes,
• taxonomy-enabled nodes.

Create any number of custom blocks (node_blocks) and automatically associate them for display on a particular (node) page view.

Useful for granting non-admin users the ability to insert
custom blocks. Developed to enable block insertion into special phptemplate regions in a node by regular users.

A new tab "info boxes" is added to the node page for adding a node_block.

Saves the trouble of going to configure the block manually in admin/block

Block display region is set in admin/settings/node_block.

On deleting the block association, the block itself is deleted from the block table.

No database tables are created by this module.

The nodelimit.module allows administrators to limit the number of instances of each type of node which can be created by users, on a per-role basis.

Each node type can have a different maximum number of nodes created for each role.

The module also provides an alternative "Create Content" page, and alternate "Create (content-type)" menu items, which may be used instead of the standard ones, (to prevent links to node types that the user has exceeded their limit on from appearing).

People may also want to check out the following project:
Nodefamily
http://drupal.org/project/nodefamily

Which apparently provides relationships between nodes, as well as allowing a limit on number of nodes per type, per user.

DESCRIPTION
This module enables users to vote on nodes. Like comment moderation, the available votes and the value of each vote is configured by the admin.

This module should be used within ecommerce package and depends on product.module.

It allows to assign a certain product type to any content type declared in the system (CCK types as well). After that all nodes of this type will be created as products without a need to add them to a store manually.

It can help to solve the following problem:
You used CCK to create a node type and are going to use it in the future for products. Users of specific role can create their own products (not only admin can do it) ... kind of auction. When going to node/add/mytype page you will see a list of product types and an 'Add to store' button. So, in order to create a product you need to choose product type and press additional button. You need to do it each time for each of your products. More then, it is not user friendly action.

This module can help you to automate this process by associating a certain product type with a desired content type. Each time you create this content type it is created as a product and all its specific fields (price, SKU) will be available on the form.

Developed by ARDAS group - Web site development, Drupal services, Software development, IT outsourcing.

讓管理者可以手動把節點放到某個群組裡，例如標示某篇文章為焦點文章，或是將重要文章在區塊裡呈現或是隨機列出。
管理者可以指定能被加入到佇列的節點類型、數量，以及能使用此功能的權限角色。

The Node Queue module allows an administrator to arbitrarily put nodes in a group for some purpose; examples of this might be to highlight one particular node, as in a typical news site's Lead Article. Another use might be to create a block listing teasers for 5 forum posts that the admin thinks are important. Another use might be to create a group of nodes, and then have a block or the front page offer one of these randomly.

This group can be re-ordered arbitrarily by the administrator, by moving nodes up and down on an easy to use screen.

[8/28/07] I have released Nodequeue 2.0 RC. I believe this version is just about ready to go, but since it did entail a significant rewrite of the code, I would like a slightly wider base to tell me that it actually is. If I don't see any bug reports in about a week I'll roll it 2.0 and set the 2.x branch to the recommended version.

Note that the 4.7.x version of Node Queue is getting only bug fixes at this time; and even that is iffy. If anyone is interested in supporting Node Queue for 4.7.x, I will likely only fix obvious bugs or commit patches to the 4.7 branch.

This module enables access control based on (and so requires) the Node Relativity module.

Node Relativity "allows parent-child relationships between nodes to be established, managed and searched" and makes it very easy to create child nodes with a click. Node Relativity Access Control restricts access to nodes that are in relativity relationships.

Node Relativity Access Control is unique as a user access module in that it gives a user granted access to a node and to all that node's progeny as well.

By default, each node's author is granted this access to children and grandchildren (and so on) nodes.

Optionally, CCK userreference fields associated with a content type can be given special access settings.

Users can also be added specifically to the node.

Sponsor: Mac Clemmens, Digital Deployment.

Special thanks to Karen Stevenson for explaining how to find the right table for a given field using Drupal's API.

The node style module is a simple module that allows per-node customisations by overriding PHPTemplate variables.

Example scenarios where this module will be useful:

• You have a node that you've promoted to the front page and want to hide side bars, submission information and other node and page elements to get a "welcome" page appearance.
• You would like to insert stylesheets or javascript files for specific nodes.
• You want to use different themes on a per-node basis.

N.B. This module works at the theme level and might not necessarily be the most efficient way to accomplish a task.

Ideas on improving this module are welcome.

This module provides a separate teaser field.

This provides three advantages to the standard teaser system:
1) It allows users to specify a totally distinct teaser, like a
summary or description, that does not contain any node text.
2) TinyMCE attempts to encode the <!--BREAK--> normally used for
creating teasers. This circumvents that problem.
3) Users more familiar with Movable Type, Text Pattern, and the
like will be more comfortable with this interface.

讓使用者可以針對內容進行投票，可以顯示出每個內容節點的平均分數和投票數。如果使用者沒有投票，將無法看到投票結果。其他功能包括：

• 提供了顯示最高票數/分數的內容、投票最多的使用者等區塊。
• 可以設定哪些角色的使用者可以投票或是看到投票結果。
• 可以設定針對哪些內容類型進行投票。
• 如果安裝了 user points 模組，使用者可以透過投票賺取點數。
• 可以使用星號或/和文字來呈現投票分數。網站管理者可以修改星號的外觀圖檔。
• 投票結果可以顯示在摘要或全文模式裡。
• 使用者可以對自己的內容投票。
• 使用者可以改變投票分數。

Nodeaccess 可以在 Drupal 中控制節點存取權限的一個模組。

可依照群組角色或個別的使用者，針對每一個節點加以設定瀏覽、編輯和刪除的權限。安裝後會呈現在每個節點的控制 tab 中。

與 simple access 模組的比較：

1) simple access 只能限制群組角色，nodeaccess 可以限制群組角色和個別用戶。
2) simple access 只能控制能否瀏覽，nodeaccess 除了可以控制瀏覽之外，再加上控制編輯和刪除的權限。

Nodeaccess is a drupal access control module which provides per node access control. Users with the 'grant node permissions' access control will have a grant tab on node pages which allows them to grant access to that node by user or role. Administrators can set default access controls per page type, and also define which roles are available to grant permissions on the node grants tab.

1) simple access only deals with groups of roles. nodeaccess deals with users and roles.
2) simple access only deals with viewing nodes. nodeaccess deals with editing and deleting as well.

Nodeauthor module is very simple module which allows users to edit additional
information about them in user-edit form. This information is then displayed
below nodes created by such users.

New feature: Allows displaying user picture in author information. (Only in 5.x)

Administrators are allowed to restrict displaying info to particular node types.

This module was sponsored by Drupal CZ site and Pavel Procházka.

Provides popup windows and bookmarklets to submit new nodes with ease.

Popup windows can be accessed with links generated by the function nodeformpopup_l, or with the bookmarklets supplied in the apposite page. Bookmarklets pass the current page's URL, title and selected text to the node form via a query string like this:

http://www.example.com/nodeformpopup/node-type?url=currenturl&title=currentitle&description=selectedtext

It works in team with nodeformtemplate, and should work with other modules implementing a similar scheme too.

Popups/bookmarklets can be enabled in the content types settings for each content type.

As a bonus feature, you can enable "shortcut links" for CCK types: a link to a popup form will appear beneath each nodereference field for each referenceable type.

The nodeorder module gives users an easy way to order nodes within their taxonomy terms.

By default, the taxonomy module orders listings of nodes by stickiness and then by node creation date -- most recently posted nodes come first.

The nodeorder module gives the user the ability to put nodes in any order they wish within each category that the node lives.

There are two ways that a user can order nodes within a category. The first is to use the "move up" and "move down" links that can be configured to appear on each node (especially useful when looking at lists of taxonomy terms). The second is to use drag and drop, which appears on the administrative listings of nodes in a category.

The drag and drop ordering is built upon the jQuery Interface Sortable plug-in and, in Drupal 5.x, depends on the jQuery Update module, the jQuery Interface module, and the jQuery Interface Sortable module.

Add tabs to existing nodes to create new related nodes. By creating nodes in context, the user avoids having to select the referenced node manually.

Requires

• Nodereferrer module (working version here)
• Nodereference module from CCK

This is a by-necessity fork of nodereferrer module. I has a number of patches applied from nodereferrer's issue queue, but future patches should be attached to the forked project.

Goals

• Work well on D5
• Move towards a merge with nodereference module in CCK

This module adds user reviews to specified node types, on multiple axes and with voting via the Voting API module (required). It uses the Views module (required) for some displays.

It also demonstrates a simple and easy way to have nodes whose content are dependent on a related node, and cannot be created otherwise.

Notes on version status:

• Drupal 5: This is the maintained version of the module. New features will be added only to the current version.
• Drupal 4.7: This version of the module is frozen. I will only be adding bug fixes.
• HEAD: This release isn't tagged for a reason. Don't use it. Ever. Its status id "undefined".

Allows a blacklist of sites that will have a rel="nofollow" attribute added to their link tags whenever used on your site. Currently the only page in the blacklist is Wikipedia, though allowing an admin controlled blacklist and whitelist would be useful enhancements.

You must configure the input formats and add this to a format for this module to work.

A very simple module which provides a way for users to have a 'notepad' area where they can record any arbitrary text.

Notes are defined as a new node type and are listed in a block or a summary page. Notes consist of a title, a body (subject to filters) and a priority which governs the list in which they are displayed in the summary page and block.

NTLM Authentication module using simple LDAP connection to Windows Active Directory for further authentication. This is still in development, first release for testing purposes and not to be used in production environment. The module is aimed at those who want LDAP Authentication with the option of NTLM, but also require something a bit more easier and simpler to use that will work with Windows Domain Controllers.

There are no known issues with the code as of yet, it is based upon the ideas from the 'LDAP integration' module http://drupal.org/project/ldap_integration so it has the same interface form as the LDAP server setup pages, it has less features but is far more lightweight in comparison. This LDAP module is designed to work with Windows Active Directory and has only been tested in an Active Directory environment using Windows Server 2003 Domain Controller.

By default NTLM authentication is disabled, to enable this you must go into the administration panel and enable this feature.

License: http://www.gnu.org/licenses/gpl.txt

Nutch is a web crawler/indexer/search engine that is based on Lucene. It is a Java tool. This module allows you to have basic control over the Nutch crawl lifecycle through the Drupal web interface. Combind this module with the OpenSearch Client module and you can offer the search results through Drupal as well. This is a work in progress and participation from Nutch and Drupal developers is wanted.

There is no documentation yet, but if you are familiar with Drupal and have managed to get Nutch running from the Nutch documentation, you'll figure the rest out.

There is now a working group to discuss this module and other Nutch/Lucene related efforts: http://groups.drupal.org/lucene-and-nutch