Last node 模块能快速访问最近发表的节点，它只按日期排序节点。
通过这个模块，可以通过类似 ?q=last_node/story, ?q=last_node/page 的地址访问不同类型节点的最新列表。

Last node 提供了：
用于建立 “首页” 的简单 api，只要一行就能得到一个最近 x 个节点的列表；
一个最近节点的区块；
一个显示所有最新节点并带滚动的区块；
为每个节点类型提供 feed 页面；
你可以设置最近节点的关联图片。
Last node vs Views: 本模块并不额外建立新的数据库表，它非常快速，易于使用； views 模块功能完整但复杂的多。

Lazy registration implements lazy registration for Drupal.

It can create accounts automatically, purge them after a period of time, allow users to make them permanent by either email confirmation or a simple edit to the account.

This module allows users to authenticate against a LDAP directory. It can preserve LDAP groups as Drupal roles. In addition, the newly added ldapdata module also facilitates management of LDAP data from within Drupal

5.x-1.3 version has been released. Please download this release before reporting any bugs!

IMPORTANT NOTE: Anyone interested in helping with maintaining and enhancing the module, please contact scafmac or kreaper.

(2007-07-30): Version 1.9 for Drupal 5.x out now!
(2007-03-28): Screencast on how to install leech: http://youtube.com/watch?v=nRmd6whQFlY - thanks to streamcast.eu

Leech is a module for downloading articles from feeds to a Drupal site.

Items aggregated from a feed can be turned into any node type. Likewise, feeds themselves can be represented as a node type of choice.

Leech integrates with Organic Groups: feed items inherit their feed's group settings.

The add on module leech_yahoo_terms allows autotagging of aggregated articles with the Yahoo term extraction web service. (With version 1.7 leech_yahoo_terms has been replaced by the yahoo_terms module.)

Leech comes since version 1.2 with an interface to the URL profile module. URL profile allows you to trace the origin of aggregated articles and retrieve information about the article's sources from technorati or alexa - particularly useful when dealing with feeds that contain articles from different origins. (Learn more about URL profile )

这个模块在用户注册的时候，显示你的服务条款/使用条款，并要求接受条款才能注册。

在註冊時顯示網站的使用條款，使用者必須接受使用條款，才能完成註冊程序。

在用户注册时加入“我同意。。。条款”的过程。模块本身不带有具体条款，需要管理员自行加入。本站用户注册处也使用了这个模块，注册时就可以看到。

• A generalized database for storing legislative data, such as bills, politicians, and votes.
• Import scripts to fill this database.
• Does not especially provide an API or UI at this time; all you get is a database.

Currently supports only the U.S. Congress, primary data source is http://govtrack.us/. Iowa, Ohio, and California legislatures are being worked on. Post an issue if you are interested in developing others.

A very simple Customer Relationship Management module that allows site admin to reply to support requests.

- The module can be configured to notify users when a support request has been replied to.
- The email message can be configured
- Roles can be selected to be notified when a new support request is made
- A new menu item called lightcrm is added to the user menu

No database changes required. The module uses the comment module. A new block called lightcrm is created and displays to users if there is a new reply from admin, when the user logs in. Site admin view suport request by clicking on comments menu. A new node type lightcrm is created.

The Lightbox module is a simple, unobtrusive script used to overlay images on the current page. It's a snap to setup and works on most modern browsers.

A CCK content field which lets you add a complete link to your content types; including URL, title, and optionally a target attribute.

Requires the content module (CCK).

This module requires tinymce.module.

The linktocontent module allows you to extend the tinyMCE editor by several plugins.
With these plugins you can link to nodes or menu items or user profiles (planned for drupal 6.x).

The links block takes all the links which are generated by nodes, and provides a block with a list of these links.

Badly seeking comaintainers.

The Liquid Wiki Engine Project aims to build a module providing wiki funktionality to Drupal.

Important: Please download the current development release (HEAD). Some important changes has been applied.

Note: The 4.7 branch is no longer being developed. It contains heaps of bugs and should not be used. Please don't submit issue-requests on this version.

Live Discussion 模組會建立一個區塊，列出最近有回應的文章列表。你可以設定文章列表的數量（5/10/15/20/25/30），文章標題後面會顯示回應的數量。Live Discussion 模組也提供了一個頁面，可以讓已登入的使用者追蹤一個月裡未閱讀過的回應。

通过区块显示最新评论。与drupal自带的“最新评论”不同的是，显示的不是评论本身而是原文的标题，并在后面加注有多少篇评论。例子可以看右边栏的“Live Discussion”区块，也可以看这个站点。

Live Search aims to provide Drupal's search module a live search functionality through Ajax and to degrade gracefully to a normal search box when the user has JavaScript turned off. It has the following features:

• Choice between theme-provided or module-provided search box. Live Search builds upon an existing search box. Most themes provide their own search box, and the search module itself also provides a search block. You can choose which search box to enable live search functionality on.
• Compact search box. This enables the search box to behave in a more Apple style, such as the lack of the "Search" button, with the "Search" phrase embedded in the text field itself.
• Ajax request firing delay. To save bandwith and ease server loads, an Ajax search request is fired, by default, after the user stops typing the keyword for 1250 milliseconds.
• Snippet and node info hiding. To save screen real estate, you can opt to hide the snippets (excerpts), the node info (showing various information such as node type, author, and date), or both.

Live Search fully utilizes Drupal 5's built-in jQuery JavaScript library.

This module allows you or your users to automatically crosspost entries to a LiveJournal account. It is based upon the excellent work of Evan Broder who wrote a WordPress plugin of the same name.

Currently this module needs further testing but appears to basically work. CVS is for Drupal 4.7, please use that for now.

This Module integrates the famous 'Liga Manager Online' into Drupal.

It is very alpha and you should not use it on productive sites but I want to give the possibility to discuss about the project and to submit your feature requests. In this time the module only integrates the LMO into your Drupal so you can use it here as you normaly would use LMO itself.

- 4.7 Download works with Drupal 4.7
- cvs Download works with Drupal Head (5.x)

Plans for the next days:

• Filter to insert leagues, standings and match results into your nodes
• Connection to 'og_teampage' module to show up standings and match results into your teampages
• Blocks with standings, leaques etc

A framework for running and building load tests on a Drupal site.

The goal of this module is to allow site administrators to run benchmarks of there website under various configuration settings to help find bottlenecks and other issues that might be slowing down their site. It also targeted towards developers who wish to design load tests for their own modules.

Use Cases

One of the built in test suites that can be used automatically runs through the list of enabled modules and runs load tests on each module individually. At the end of the test run the user can view the duration of each test and will be able to see if it ran significantly slower when any particular module was enabled.

More involved load testing can also be done using pre-configured states. For example, a developer might write a patch against core and want to see what the effect the patch might have on the site load. They can set up a number of states each with different configuration settings and setup a script (maybe using ab2) to run a series of tests against the site and automatically changing the state when each test is done.

Writing load tests

Writing a load test is almost identical to writing a simpletest test. There are two key differences:

The localization client project (formerly known as live translation) provides live site interface translation updates from a known localization server (see l10n_server project for more information on that).

Read more

The README contains more information and we have a TODO list. Look into the Localization server project for more information.

Sponsors

This module was originally sponsored by Titan Atlas (http://www.titanatlas.com/), a brazilian computer company, and is now sponsored by Google Summer of Code 2007.

The localization server project (formerly known as lt_server) provides a community localization editor, which allows people from around the world to collaborate on translating projects to different languages, especially for Drupal. It is inspired by Launchpad Rosetta (https://launchpad.net/rosetta) but is highly adapted to Drupal needs.

The module suite solves the Drupal project translation problem with a web based interface. The various Drupal projects release source code on a daily basis. The goal is to help translators to keep up with this pace by sharing already translated strings and distributing translations effectively.

Read more

The README contains more information and we have a TODO list. Look into the Localization client project for more information.

Sponsors

This module was originally sponsored by Titan Atlas (http://www.titanatlas.com/), a brazilian computer company, and is now sponsored by Google Summer of Code 2007.

The Localizer module extends Drupal's ability to handle human languages. It provides control over a site's user interface language, the ability to enter and control content in multiple languages, and the ability to display the correct language content needed. The module has been designed so that only the features needed for a particular site need be implemented.

Localizer allows translation of the following system objects:

• Blocks
• Menus
• Nodes
• Taxonomy
• System settings (variables)

Additionally, there is built-in support for the following contrib modules:

• Views

More informations

If you want to support this project, take a look at this page :
http://www.speedtech.it/drupal-content-localization

Currently, location.module supports proximity searches for content. Content (i.e., 'nodes') can be tagged with a physical snail mail location (whether full or partial). What number of location fields (e.g., 'street', 'city', 'postal code', 'country', 'province') are collected for each node type (and whether they are required or optional) is configurable in the default workflow for each node type.

Ultimately, it is possible to use the API without any of the node features provided by location.module. However, location.module must be enabled to use the API. If you just want to use the API and not any of the features of location.module, you will want to enable the module but turn off all location collecting for nodes. There is also a settings page for some basic settings. As of the first CVS commit, the API is not finalized and is subject to change. Developers are encouraged to examine it for ideas. Right now there is room for improvement in terms of memory and speed for proximity searches (geospatially chained search caching is implemented, but the building of the results can definitely be improved).

If you have any good ideas for improvement, please submit a patch to the queue, or describe it to me in the issues queue for this project.

Stay tuned for updates. We plan the first release of this project in the month or so after the 4.6 release.

Hierarchy allows administrators to create a dynamically created taxonomy hierarchy for locations. It links the terms into a structure that looks like this:
Country
--State
----City -> node
Administrators are allowed to run this for any content type. An example would be using it for the user node type. What this does is if a user has a location, anytime they update their city, state, country, the hierarchy module will create/delete/update hierarchical taxonomy term based on that data. It will then link the city to the node being edited.

This module is useful if you want to allow users to browse for other users (or any content type for that matter) by location. For testing, I would suggest using the directory module.

Log Watcher allows you to monitor your site logs in a systematic way by setting up scheduled aggregations for specific log types. For example, if you want to keep tabs on your "page not found" logs, you might create a job that sends you the top 25 "page not found" errors every seven days. The latest run of any given report is also available from the administration screen, so you can view them on demand as well.

To set up email reports, assign users who should get the reports to the "administer logwatcher" role. The module depends heavily on the availability of a crontab.

This is a collection of logging and alerts modules. They interface to the new custom logging watchdog hook available in 6.x.

Currently, the following modules are included:

Email logging and alerts

Allows routing of watchdog messages to various email addresses, based on their severity levels. For example, emergency and critical messages need to go to a pager or mobile phone email address, while debug messages go no where.

Author

Khalid Baheyeldin of 2bits.com.

The author can also be contacted for paid customizations of this module as well as Drupal consulting,
installation, development, and customizations.

This module controls where users go after logging in. You can configure login destination on a settings page. It will be either static URL or a PHP snippet evaluating your own site's logic. You can also configure which pages redirection is applied.

To achieve this you can specify either a list of URLs or a PHP snippet to build this list dynamically. So, you can redirect user to various pages depending on which pages they are logging from.

upal provides a logout link for authenticated users, but does not provide a login link for anonymous users. This module provides that.

This handles issue http://drupal.org/node/74706

Code is a revision to Heine's code at http://drupal.org/node/14223#comment-105408

This is a pure API module, providing functions for generating login tickets.

A login ticket consists of an automatically generated pass code, an expiration date, and a user who may log in with the pass code. This module provides functions for generating, retrieving and deleting login tickets, as well as checking validness of a given pass code and, given a valid code (while not requiring username and password), logging the concerned user in.

Login Toboggan 模块会接管 Drupal 的登录系统，它提供了一些高级功能：
允许用户通过用户名或 e-mail 地址登录。
允许用户自己定义自己的密码（当然 Drupal 5 也可以自己设置密码了）。
允许用户注册后立即登录（好像 Drupal 5 也可以）。
为拒绝访问的页面提供登录。
提供两个登录区块选项: 一个用 JavaScript 技术，另一个将用户引导至登录页面，登录后返回之前的页面。
可定制的注册表格，并用两个 e-mail 字段预防输入错误。
可选择引导 “立即登录” 的用户到一个特定的页面。
可选择引导 e-mail 验证成功的用户到一个特定的页面。
可选择提示用户登录成功。

修改 Drupal 原有的登入系統，提供以下功能與改進：

• 讓使用者使用 username 或電子郵件位址來登入。
• 可以讓使用者自訂密碼，立即登入，不經電子郵件確認。
• 在拒絕存取頁面，提供一個登入表單，讓未登入的使用者可以直接登入。
• 提供兩個登入區塊選項：一是採用JavaScript，在點選登入時即時呈現登入表單；另一是導到獨立的登入網頁進行登入，登入後會導回原頁面。
• 修改註冊表單，讓使用者必須輸入兩次電子郵件位址，避免錯誤。
• 可以讓使用者在登入後，導到特定頁面。
• 可以在認證電子郵件位址後，導到特定頁面。
• 可以顯示訊息以告知登入成功。

A simple tool to display either a random logo on every page refresh, else display a specific logo on specified pages and a default set logo on all unspecified ones.

Lets users vote 'love' or 'hate' on the terms of a particular taxonomy vocabulary. Each user's loves and hates can be displayed on their profile, and the /lovehate page shows the popularity of each term. The pages and lists are simple, but flexible: every byte of HTML the module generates can be themed. Loves and Hates requires the VotingAPI module, and (obviously) the Taxonomy module.

Loves and Hates was sponsored by the fine folks at Lullabot!

Lucid menu is a highly customizable javascript menu which replaces the current menus with new ones.

Its idea was heavily influenced by nice_menus but attempts to provide more customization options.

Almost every aspect of this menu is customizable. It uses the doIMenu 1.5.3 by Donna Iwan Setiawan, this release is a beta release. Feedback is always welcome. Customization may be needed in a fresh installation to get it up and running.

Contributed by : Ashraf Amayreh

Sponsored by : E-rize