Backlinks module provides a "what links here" filter for Views: give it a nid (via URL argument, for instance), and it will generate a list of all nodes linking to that node, courtesy of search module's index.

After enabling the module, two pre-configured views will be created for you: a "backlinks" tab view, and a backlinks block view, which generates a block with a list of backlinks on each node page (after you enable it at admin/build/block). With the Views UI module, you can configure these at admin/build/views; you may want to turn off the menu tab, add an RSS feed argument, change the view type, etc.

To-do: add a forward-links functionality.

The Backport module makes selected core Drupal 4.7 methods and tools available to 4.6 modules. Initially included are portions of the Forms API and the Javascript tools.

Using Backport, developers can construct forms using the Forms API in 4.6 modules and can use the drupal.js methods and widgets.

Note that this module is has had only basic testing.

This module creates a tarball that consists of your Drupal database and all files under DOCUMENT_ROOT, which can then be downloaded through your browser. It is useful for performing backups of entire Drupal-powered websites.

Update! Version 5.x-4.x is available. Details and the download are here.

Bad Behavior is a set of PHP scripts which prevents spambots from accessing your site by analyzing their actual HTTP requests and comparing them to profiles from known spambots. It goes far beyond User-Agent and Referer, however.

banner.module 可以在 Drupal 網站中隨機播放廣告，並且統計顯示與點閱次數。註冊用戶可以擁有自己的廣告，編輯、查閱報表。

廣告呈現的素材，支援 flash、文字樣式、以及一些常見的圖檔格式。

自动轮换显示广告条。管理员可以方便的查看点击统计，并预设/开启/关闭/批准特定广告，用户则可以查看/修改/上载自己的广告条。

The banner.module allows you to display ads on your Drupal website. It randomly displays the banners, and automatically tracks how many times each is displayed and clicked. Users of your website can be given ownership of banners, and be allowed to modify certain settings and view statistics.

Supports numerous graphic formats, flash animations, and text.

The Drupal bbcode.module adds a BBCode filter to Drupal. This allows you to use HTML-like tags as an alternative to HTML itself for adding markup to your posts. BBCode is easier to use than HTML and helps to prevent malicious users from disrupting your site's formatting.

See the help screen of the module (or the code) for information on which tags and variants are supported. This implementation is not necessarily the same as the original BBCode implementation.

Note that this filter also recognizes and converts URLs and email addresses to links automatically.

The quicktags module can be used in conjunction with this module to provide a BBCode formatting bar above all textareas.

In Drupal 4.7, 'date' type form fields cannot distinguish between required and non-required fields. In both cases, a user must enter a date, even if the field has been designated not required (e.g. a birthday profile field was set up as optional, but the user must still enter a date).

This module, once enabled, will silently find all date fields and exchange them with 'better date' fields. Better date fields allow users to enter null dates for non-required fields. For required fields, behavior remains the same. For the purposes of theming better dates appear as dates.

Bind is an administration module for managing DNS zones for BIND via Drupal. Supports per-user administration of zones and error checking. Demo and screenshots available. Demo in the making.

The Bio module allows each user to create one (and only one) "bio" node. Any node-type can be assigned as the bio or Bio module can provide its own node type. The bio can display on the users' profile pages and/or it can add "View [username]'s [Bio]" links to nodes.

Combined with CCK in Drupal 5, Bio module can provide a more flexible, more *efficient* solution than Drupal's core Profile module. If you've wished that user profiles were complete first-class nodes -- available to your content search index, available to nodeapi-based modules, and themable through node-[bio].tpl.php, then Bio module is a quick-and-simple way to go.

The Birthdays module allows users to add their birthday to their profile. It lists birthdays on a seperate page and in different blocks. Users can receive an e-mail on their birthday automatically, and the administrator can receive dayly reminders of who are having their birthday. Requires Profile module from core.

This module provides two items:
- A Torrent node type
- A BitTorrent tracker

The torrent node type allows users to upload a torrent along with a description. The type may be configured so that the announce URL is automatically changed to a specified value.

The tracker portion will track any torrent that has been uploaded to the site. The administrator can enforce share ratios and maximum number of simultaneous downloads. It operates within one of three "scopes". The scopes determine the amount of statistics collected as well as the level of security for the tracker. The "public" scope allows anyone to use the tracker and minimal statistics are collected. The "mixed" scope still allows anyone to connect to the tracker, but the users who connect with a passkey have specifics collected about their tracker usage (upload and download amounts). Finally the "private" scope requires a passkey and collects the same statistics as the mixed scope. Also the user's permissions are checked to verify that they are indeed allowed to use the tracker.

The web-seeding extension to the BitTorrent protocol has also been implemented allowing the server to act as a seed when no other seeds are available. The module implments both the GetRight and BitTornado specifications to support a larger audience of BitTorrent clients.

TODO:
Simpletests
Clean-up "edit" performance

Overview

This module provides an alternate way to manage blocks. If you have many blocks that are displayed in different configurations across your site's pages, managing them through the standard blocks admin interface can be tedious. For example, say you decide you want to add six blocks to three different pages based on request URI and four blocks (including two of the original six) to three other pages based on node type. This quickly becomes a frustrating exercise as you think through writing logic per block that will handle the overlap correctly. Block Assign simply provides another approach to organizing blocks.

Usage

1. Enable the module in your site admin.
2. Go to blocks admin and configure a block.
3. At the very bottom of the block form, you'll see a text blurb telling you what to paste in the PHP eval textarea (also assumes you've checked the PHP eval box). This blurb will differ per block, as it sends module and delta back to the function to be evaluated.
4. Repeat the step above for any blocks that should be subject to the block_assign module. If you need to include other logic in the block, you can do that as well, and simply integrate the suggested code into your own logic. Future versions of the module will probably make this step less painful.
5. Go to /admin/settings/block_assign

The Block Bar module is a block module that acts as a container for other Drupal blocks. The module builds an Outlook style collapsible menu bar from the child blocks with each child block representing one panel within the bar. Multiple BlockBars can be created. Each BlockBar can be set with "sticky panels" which will remember the panel's open/close state between page refreshes. Also, an option can be set that will only allow one panel to be open at a time for a given bar. Block Bars and Block Bar panels can be themed globally or individually.

Screenshot of BlockBar in default theme.

Screenshot of BlockBar with embeded Control Panel module.

Screenshot of block configuration page.

Screenshot of BlockBar settings page.

** NOTE! **

This module creates a cached version of each block. Block caching happens separately from page caching and so it will work for logged-in users whether or not page caching is enabled for the site. Cached blocks make just one call to the database and can therefore reduce the overhead required to render blocks that require complex queries and/or calculations such as some Views or Taxonomy-related blocks.

When this BlockCache is enabled, administrators will see a duplicate "cached" version of each of the site's blocks. By enabling the cached version (and disabling the original version), you can display a block that is physically identical to the original, but is loaded from the cache rather than calculated for each page. This can greatly speed up the rendering of a page. There are options for how and when the cache is refreshed and whether it is cached for the whole site or on a page-by-page basis.

Block region is designed to address the following issues and bugs that may crop up in block configuration in Drupal 4.7 installs when multiple themes are present:

1. Configuring settings separately for each theme is awkward/error prone
   Some users have complained that block configuration is difficult for multi-themes in 4.7, because each block status, weight, and throttle settings need to be made separately for each enabled theme. This simple module provides a fix, allowing the configuration of these block settings for all themes at once. "Placement" (which region to put the block in) becomes the only setting still configured separately for each theme.
2. Only the default theme displays on block configuration (other themes look the same as default), and all settings, including placement, are applied to all themes.
   When trying to configure blocks by theme, an issue with theme initiation may cause only the default theme to be displayed and all themes to get the default theme's settings. With blockregion in place, each theme will be configurable again.

Enable this module and admin/block will provide global block settings (the default theme). Block configuration for other enabled themes will allow only "Placement" (selection of region).

此模組會在 user profile 裡加入兩個欄位，讓有權線可以寫部落格的使用者在裡面填入部落格名稱和描述，並把這些資訊顯示在一個區塊裡，此區塊僅會在該使用者的部落格和部落格文章裡顯示。

The bloginfo module adds a blog title and description to your blogs. It is a simple module that adds 2 additional fields to the users account screen, for those who have permission, to have a blog title and blog description. These are then put into a block that can be placed like any other block. The title is the block title and the description is the block content.

The idea is to have a blog title and description like one via blogger.com.

The block will only display on a users blog list or blog post who have filled in the settings.

Blog theme allows users to have persistent themes for their blogs based on the theme they choose for their account. When others view thier main blog page, or any node created by them, the reader will see the authors theme instead of their own.

Blogger module used for:
1. Display list of bloggers. You can limit how many bloggers displayed.
2. Display number of written blogs or not, i.e: Samuel (5), Linda (4), etc.
3. A "read more link" to show all bloggers with pagination support and their latest blog.
4. You can choose selected case formats: Upper, Small, or Wordcase.
5. Order by: none (random), name or blogs count.
6. Support Avatar on block and page.
7. You can set avatar size: original, width x height, keep aspect ratio.

Other contributors:
1. Daniel: spelling and capitalization corrections.
2. fkramer: fixs show latest blog.

Small module to accept blog entries via HTTP POST from AQL's SMS to HTML gateway.

[19/07/06] Now supports posting to other node types than just blog.
[19/07/06] The default title can now be changed in the blogsms settings.

This module acts as a digital notary for Drupal; it creates notarized/certified timestamps for content. When normal Drupal content is created, an easily modifiable timestamp is created. It is impossible to tell with any real certainity whether or not the node was created at that time. A certified timestamp guarantees the content was created on the timestamp indicated.

This tiny module provides a new tab which allows a user to post a new revision of the body of a node only, this is, she will only be able to edit the body of the node. No other part of the node form is shown, besides the title for information only (no editable). In order to have this functionality without having to give 'administer nodes' permission to the user, this module needs a patch for the node.module. This patch creates new permissions on revisions and nodes (delete).

This module attempts to correct a problem with the creation of book pages. Currently when you create a book page, you are free to add the page where ever you want, with any other book page you want, regardless of access control and other restrictions. With this module, an administrator can define a filter (the current filters are by role, by user, or by Organic Group) and then when a user (other than user 1 who is still free to add pages anywhere) tries to add a page, the list of parent pages is restricted to the filter.

If you have Organic Groups enabled, unless you install this module before any groups are created, you can have quite a lot of work to update the database to reflect the changes. This module automatically creates a top-level book page for every group that is created, and when users try to add pages to their group (using one of the views on the side) they are automatically restricted (assuming you have set the filter appropriately) to creating sub-pages of that new book.

A recent update to this module means that it seems to work properly, although I have not had a chance to test it when using the 'Private' module.

The Book Import module allows the importing of Drupal books, from exported Drupal book XML files. Being able to export books in this way permits bulk/offline editing, importing of books from external content, and moving of books between Drupal sites.

Please be aware that this is somewhat new code - make sure that you back up your Drupal database prior to using this module to import books.

I'm interested in hearing about your experiences with this software. Feel free to contact me via the contact form; please report issues via the Drupal issue tracker:

一個新的節點類型，內建多個與書籍資料相關的欄位，包括書名、封面圖片、出版者、作者、網站連結、版權、ISBN、頁數、價格、摘要、目錄、評論等，並可連結到外部的網路書店。

定义了特殊的书评节点，方便发布图书评论。

The book review module allows a site to publish book reviews. A book review is simply a glorified node, providing custom fields that are appropriate to writing a book review.

This module allows an authorized user/administrator to modify the tree structure of a book using a graphical interface and then update the database to reflect those changes. At some point the Javascript in the background that creates the GUI will be updated, but for now all you can adjust are the parent child relationships of the books (including splitting a book into pieces, and merging books) and not the relative weights of the pages.

As this module is still experimental, you should not use it on a production site, use it on your sandbox sites until we have ironed out all the bugs.

There have been some major updates on this module. It now includes a link on an Organic group homepage (assuming you are using the partner module, Book Expand) that allows users to edit their books using the GUI. Very useful. Also, there has been a complete rewrite of the GUI which makes it much more user friendly. Check it out!

Just as soon as I can create some GPLed versions of the images this module needs, it will be available for download. Please be patient.

For more information, contact the module author at david_wees@yahoo.com

Enables your users to place a bet on virtually anything; you decide which bets you offer. After the outcome of the bet offer is published, the module automatically calculates the amount of points each user gets.

This module provides static page caching for Drupal 4.7 and 5.x, enabling a potentially very significant performance and scalability boost for heavily-trafficked Drupal sites.

For an introduction, read the original blog post at:
http://bendiken.net/2006/05/28/static-page-caching-for-drupal

More technical details in this great write-up by Justin Miller:
http://codesorcery.net/2007/07/23/boost-your-drupal-site/

Fully customizable table gallery of quality-scaled images from a defined folder.

• Configurable image size, number of columns, background colour.
• High quality image re-sampling.
• Automatic re-sizing of both landscape and portrait images.
• Browsing images via slick Lightbox V2 or Thickbox.
• Works both in page and block mode.

Planning to do very soon:
• Possibility to configure multiple galleries.
• Adding captions to display in the Lightbox or Thickbox overlays.
• Caching of the thumbnails to increase loading speed.

Development of this module is sponsored by Vacilando.org.

The browscap module provides a replacement for PHP's get_browser() function. get_browser() is difficult (or impossible) to configure for most users in shared webhosting situations, and requires attention to keep the underlying data (browscap.ini) up-to-date. This module avoids the configuration issue by storing the data in a database table, and the freshness issue by automatically retrieving the latest data on a weekly basis (if cron.php is run regularly).

Also, statistics on browsers visiting the site may be captured by enabling monitoring in the browscap settings.

This module allows you to specify a list of browsers that your website does not support or are only semi-supported. The motivation behind the module is so that web developers can concentrate on building their site for recent browsers and ask their users to upgrade if they use an older browser that does not display the site properly.

Unsupported browsers will be shown the sites maintenance page with a custom message while semi-supported browsers will get a javascript alert or a drupal message.

You can allow users to forcefully view the site even if they are using an unsupported browser after they have viewed the maintenance page.

The Buddy API is a module to create buddy relations. At the moment there are two types of buddy relations:

• one-way relations: UserA adds UserB to his buddylist. (like a bookmark)
• two-way relations: UserA requests to add UserB to his buddylist. UserB can accept or decline the request

This module has no UI and will not do anything by itself.

讓你可以把其他網站使用者加入到你的好友名單，並可分群組、關注他們所發表的內容，有助於以Drupal來建立一個社交網絡。
Buddylist還可與其他模組整合，例如Invite，自動將受邀請的使用者加入為好友。

用户可以编辑自己的好友名单，同时显示‘好友的blog’区块。

文字編輯工具，協助妳快速地加入一些 HMTL 標籤，功能包括：

• 可透過管理介面自訂編輯介面與按鈕。
• 可針對不同的角色或使用者，提供不同的編輯介面。
• 可以使用圖片或文字按鈕。
• 可以設定按鈕的作用是要產生程式碼、 HTML 標籤、bbcode 標籤等。

預設的按鈕包括了：

1. 插入/編輯圖片：如果有安裝 IMCE，將可以直接瀏覽/插入網站裡的檔案。
2. 插入/編輯連結。
3. 粗體字。
4. 斜體字。
5. 有序清單。
6. 無序清單。
7. 摘要斷行符號（<!--break-->）。
8. 預覽：可以圈選部份區塊作預覽、或是預覽全部。
9. 說明。

感覺比 quicktag 更好用、更有彈性，卻又不像 TinyMCE 等工具那麼複雜。

A plain textarea editor aiming to facilitate code writing.

• Editor interface and button functionality are completely customizable through administration pages.
• It supports role based editor interfaces.
• It's possible to create image or text buttons.
• Buttons can be customized to generate code snippets, html tags, bbcode tags etc.

It comes with a default editor that has predefined buttons. The default buttons are:

1. Insert/edit image: Inserts image html. Make use of IMCE javascript API for file browsing, if it is installed. Editing a previously inserted image is possible if the html code of the image is selected with no extra characters.
2. Insert/edit link: Inserts link html. It works the same way as image insertion.
3. Bold: Encloses the selected text with the tag <strong>
4. Italic: Encloses the selected text with the tag <em>
5. Ordered list: Converts the lines in the selected text to a numbered list. It is also possible to start a new list with no selection. If the selection is a list which was previosly created by this button, the lines in the text are restored.
6. Unordered list: Creates a bulleted list.