Allows the use of ImageMagick to generate labels from text, using predefined rendering options.
Provides for an upload fonts capability, using TTF style fonts.

Badly seeking comaintainers.

可以傳送電子郵件給註冊的使用者。每封電子郵件會以 node 的形式儲存在資料庫裡，並可以選擇要傳送給哪些角色，以及設定純文字/HTML、字元編碼等。

向特定用户群发送email，所发信息以节点方式存放在数据库中。4.6.0版本支持将任意类型的节点内容通过email发送给特定用户群，并且可以自动发送upload模块上传的附件。

A basic module for sending email to registered users. Email messages are saved to the database as a node for future reference. Email senders can select which roles to send to.

Note: while originally there were plans to retire this module after 4.6, users reported difficulties in getting its functionality elsewhere so the module was updated for 4.7.

Aug 31, 2007: I am currently re-writing this module, simplifying the api, and cleaning up the code...I should have the new version up here within a couple days or a week for sure.

This module is currently in beta form and lacks some functionality.

For site-admins:
This module depends on the AES and SMTP modules. You must also install a protocol module (like the IMAP API module - http://drupal.org/project/imap_api) designed to work with this module, to allow it to communicate with mail servers. Once a protocol module is installed, you are able to create server configurations for any server that's supported by the protocol modules you have installed. You will also need a module that provides the webmail interface (like the Webmail module - http://drupal.org/project/webmail) that uses the provided api.

For developers:
This module provides an api for use by 'webmail interface' modules.
This module provides hooks for use by 'protocol' modules.

Documentation coming soon...

Use this module to use a contact form with the ability to attach files.

For further information take a look here: http://drupal.org/node/68265

讓註冊使用者可以透過電子郵件，建立或修改內容和回應。認證通常是透過寄件者的電子郵鍵位址，也可以加上密碼。使用者可以使用特定格式的文字，來指定分類、摘要和其他內容屬性。

允许注册用户通过email创建/编辑内容或添加评论。

Manage multiple mailing lists through pluggable backends.

Using plug-ins, this module provides an interface to subscribe, unsubscribe and post to mailing list backends. The intended purpose is to integrate existing mailing list solutions into a unified interface for subscribers.

This module was requires Mime Mail. It does not provide an interface to create or format messages, only the ability to distribute them to the list.

This module is useful in the following situation:

You run mailman and you want to allow users to create and delete list from mailman through a web interface in a secure manner.

Main Features

• Drupal and Mailman can be installed on different machines
• Drupal communicates with Mailman via XML RPC
• Suppports SSL for the XML RPC calls
• Support Digest (preferred) and Basic HTTP Authentication for XML RPC calls
• Import Feature for existing mailing lists
• Support for controlling multiple Mailman servers
• Support for virtual domains
• Support for direct link to the Mailman web interface
• Support for limiting the number of lists a user group can create

There are two levels of access

(1) 'user': a mailing list administrator that can create new mailman lists and delete his own lists

(2) 'admin': can delete any lists administered through this module

The mailman commands are given via XML RPC. The modified client library supports SSL over a non standard port.

It's the XML RPC server's responsibility to perform the actual operations (e.g. via sudo).
Mailman doesn't have a XML RPC interface in the stock vanilla distribution

If you want to use this with mailman you'll end up having to write your own server and method handlers.

An example server implementation is included.

This module provides an interface through which users can subscribe to mailing lists run by Mailman.

The administer page allows administrators to add or delete lists and program appropriate request addresses to which commands are sent by Drupal via email. Each subscription is assigned a password which is then used by the module to automatically change subscription settings from within the module, without requiring further confirmation by the user.

Other than the original confirmation of subscription by the user, the use of Mailman as a mailing list software is more or less invisible to the enduser as all settings can be changed from within Drupal.

The combination of this module with mailhandler and listhandler modules replicates to a great extent the functionality of Yahoo!Groups or Google Groups.

Versions 4.6 and 4.7 have been tested, whereas 5.0 is still in a beta stage.

Mailsave is a module that is designed to interact with mailhandler. It will detach files that are emailed to the site and save them with the node. It can also interact with other modules such as image, to provide functions like automatic conversion of nodes to image nodes. This can be used to allow posting of pictures from devices like mobile phones.

Mailsave version 2 released - what's new?

Previous versions of mailsave performed both the processing of attachments AND the node conversion functions. Version 2 changes this model so that mailsave does nothing other than attachment extraction and saving. However, it will now call other modules via hook_mailsave and send them all the attachments, so the other modules can implement whatever functions they like.

The version 2 download package includes mailsave_to_image that is the new implementation of the original mailsave function that converts the first jpeg to an image node.

MapAPI module is a helper module for the upcoming Map module. By itself, MapAPI doesn't do anything.

The motivation behind this module was to create a game that is powered by Drupal core. The first step in our work is to release flexible API that can allow us to build that game; MapAPI is part of it.

MapAPI allows you to create game maps based on coordinates. each map can contain arbitrary number of tiles and each tile can contain any number of content items.

MapAPI was designed to be very extendable by new modules that will be introduces for the game. New modules can introduce any new serialized content array indexes to be stored in the content table. the type of information stored in the table is non-important for the MapAPI, the important part is that it can store ANY information and pass it back to the parent module for processing.

TODO: add some code examples, etc

Map module provides 3 main components:

• A new node type "map". Each map is basically a google map.
• A tinymce plugin with a map selector.
• A filter so you can insert the created map in your nodes.

Developed by OpenCraft.

The Mapbuilder module integrates the Community Mapbuilder web mapping client with Drupal.

It adds the Mapbuilder context (mapcontext) and configuration (mapconfig) as content types and can produce the corresponding xml output to be used as input to a Mapbuilder client.
A filter is added for showing Mapbuilder clients (i.e. maps) inline.

Most developments are being done on the 5.x version of this module. Differences in functionality between the releases:
* support for xml schema for mapbuilder context: ViewContext or OWSContext
* support for blocks to present an overview map, legend, scalebar, and feature info; these blocks are shown for maps that are specified as e.g. <map config="mapbuilder/config/nid" blocks="overview,scalebar"/>.

At present, PHP 5 is required to use this module. PHP4 support is now experimental in the 5.x version of this module. PHP must support curl and dom/xml functions.

The masquerade module is designed as a tool for site designers and site administrators. It allows a user with the right permissions to switch users. While masquerading, a field is set on the $user object, and a menu item appears allowing the user to switch back. Watchdog entries are made any time a user masquerades or stops masquerading.

Module has been Upgraded for Drupal 5.x. (This 4.6/4.7 version of this module was created under contract for GoodStorm by CivicSpace Labs.)

Maxlenght 可以設定任何類型中的內文字數限制，Texarea HTML 標記沒有這個 maxlength 屬性, 本模組使用Javascript 語言來補強這個屬性。

如果你有設限內文的最大字數時，計數器會告訴你還有多少字可用。

Maxlength allows you to set maximum lengths to the body field of any content type. Texarea HTML tags do not have a maxlength attribute, this module fills that gap using JavaScript.

When the maximum length is enforced for a certain content type, while editing content of that type a counter will tell how many characters are left.

Provides display handlers for the Media Field audio field.

When enabled, this module enables display alternatives for audio fields provided by Media Field. These options are available in CCK field display administration and also in Views field configuration.

Various discussions are underway as to the best ways to handle audio and video display in Drupal. This module may be deprecated when a consensus emerges and new solutions are implemented.

Requires separate download of Flash players, see the README.

Based on a patch by Eaton, http://drupal.org/node/120072.

MediumVote is based on Eaton's excellent SimpleVote module.

In learning SimpleVote and VotingAPI I wanted to extend some of the features provided by SimpleVote, so I created MediumVote to:

1) Add ajax functionality using drupal.js included in the 4.7 releases.
2) Add multi-criteria voting (on either nodes or comments)
3) A menu option to select voting mode (percentages vs scores)

4) Node-specific voting criteria (v 1.2)

MediumVote has only been tested on version 4.7, as drupal.js is required.
Also, like SimpleVote, it requires the VotingAPI module, and won't run without it.
It also requires a CSS-capable browser, or the stars voting widget (used when percentage voting option is selectd) won't display properly.

I suggest you familiarize yourself with SimpleVote, VotingAPI and the ajax Handbook tutorials, as the work on MediumVote is largely lifted from that excellent work.

Development funded by addictedtotravel.com

17 july 2007: More updates: weighted fields added!

Functionalities:

• Supports profile module and i18nprofile
• Display a tabular and sortable display of user fields, roles and fields added by the profile module
• Multiple members pages and blocks, each with their own settings
• Menu items and direct, user-set urls
• Set the amount of users per page
• Access control per role
• Option to obfuscate e-mail addresses to prevent spam-harvesting

USE THE NEW 1.1 RELEASE - it should be stable and contains bug fixes.

This module adds the ability to have several different membership types, each collecting different data from the user for registration by using custom content types and the combination of nodeprofile and pageroute modules (both required). The accounttypes module is recommended but not required. See each required module for any dependencies that they might have.

What this module does is:
When a user attempts to register for your site, they will first be presented with a drop down selector of membership types which you as admin have previously defined. They will read instructions for proper membership type selection that you previously wrote. After selecting and submitting this form, they will be presented with the standard Drupal registration form. Depending on whether you require admin approval of new accounts and/or email verification, the user will then either - a) be immediately presented with pageroute consisting of nodeprofile pages which will collect further data from them, b) be logged out so they can verify their email, then when they return be presented with the pageroute for their membership type as in (a), or c) after the admin has unblocked their account and/or the user has verified their email, when they return they will be presented with the pageroute as in (a).

In all cases, if you require that certain pages of the pageroute be filled out before the user can use the site, they will be routed to the next unfilled page at each login, or each attempt to browse to another page until they do. In other words, they will be stuck until they complete registration, except that they can logout at any time.

See the USAGE example in the README for how to setup nodeprofile, pageroute, and your content types.

Optionally, if you use my Account Types module (http://drupal.org/project/accounttypes), you can assign/associate an account type with a membership type. The README explains the difference between these two concepts and how they can work together.

This module is also aware of OG and my Content Type Administration by Organic Group module (http://drupal.org/project/og_content_type_admin). See the README for how this module interacts with these others.

The README contains the following:

--CONTENTS--
REQUIREMENTS
SETUP/INSTALL
FEATURES
USAGE (Example)
UNINSTALL
CREDITS

See the documentation link below.

This module is complicated to setup and use because of its dependencies. You must read AND UNDERSTAND all documentation for the nodefamily, nodeprofile and pageroute modules before attempting to use this one. Oh, and understanding CCK is a must as well. This precludes use by casual users, whether newbie or not. I'm willing to help, but I won't hold your hand.

This project consists of several parts:

1. An API for using Memcached and the PECL Memcache library with Drupal.
2. session caching doesn't work and has been removed
3. "Drop-in" replacement library for caching (works with cache_get and cache_set).
4. A module that provides administrative overview of Drupal's interaction with Memcached and logic to invalidate "dirty" cache items.
5. A set of tests that can be run to test your memcache setup.

This project is co-maintained by Robert Douglass, Nicholas Thompson, Simon Roberts and Steve Rude.

With this module you can split any menu block into two different blocks: a first block with the first level menu entries only and a second block with any second level and sub level menu entries. You can have as many splitted blocks as you need.

Checkout the demo site to see how this module works.

turns a menu item to a page which can display links to sub-items and nodes which are added to the tree. If the views is installed then a view can be used instead.

可以 根據 角色 來顯示 選單"項目"
例如

研究生 <- 這是選單標題
●OOO <- 這是選單項目
●XXX <- 這是選單項目
●--- <- 這是選單項目

所以當你想用 研究生角色 來顯示 研究生連結導覽時
就必須逐一在選單項目做設定
雖然較麻煩，但不用讓後續不懂資訊卻要管理系統的人煩擾。
試試吧!
相關討論: http://drupaltaiwan.org/forum/20070306/975

This module allows you to restrict access to menu items per roles. It depends on the
drupal core menu.module - just activate both modules and edit a menu item as usual.
There will be a new fieldset that allows you to restrict access by role.

Unfortunately the module requires a simple patch for drupal's menu.inc. Be sure to read the README.txt.

Type in a keyword or two, and get a list of matching admin pages back. Links are highlighted on the current page with spiffy bubbles. Deep links are highlighted with half-transparent bubbles.

Updated demo video available: http://acko.net/files/Drupal%20Menu%20Scout.mp4

It indexes the menu item titles, descriptions and help with search.module on first search (takes a couple of seconds). It does not use cron-based indexing.

Known limitations
=================
- Your admin theme must have a 'content' region. This is standard for all core themes.
- Requires javascript (degrades gracefully otherwise).

Credits
============

Authored by Steven Wittens

Provide means to allow users to modify parts of the menu without giving permissions for the whole menu structure.

Some info is available in the README.txt file.

If you want to restrict viewing have a look at the Menu per Role module.

This module adds some common-sense usability to Drupal's menu system:

• Menu Trails implements primary/secondary links which keep the current menu trail "active" or highlighted. A handy snippet ready to go into your template.php is included.
• The module provides a means of broadly categorizing nodes (by type or taxonomy) as falling "under" a known menu item. These nodes are not added to the menu tree (keeping the menu admin system sane) but they will trigger the functionality above -- preserving navigation state for the user -- when viewed.

How is this useful? Compare: BEFORE vs. AFTER

Future development will (hopefully) include integration with Views such that nodes can be classified to fall "under" any matching view which creates a menu item.

Menu Trails module was developed with sponsorship from the fine folks at Songbird.

The Menu Trim module allows menu hierarchies to be trimmed when navigated. Trimming, here, means skipping the display of parent menu items when any of some designated items becomes active.

At the simplest level, this module allows to hide a menu until some of its items has become the active item (by reaching the corresponding url). This is easier than configuring the menu's block visibility for each possible path contained in the menu.

This module can be used to make a "contextual secondary menu" based on the primary links (e.g. you set the Primary links menu for "Allow trimming for this menu, hide menu when no item is active", activate the "Primary links (Menu trim)" block, then edit the menu's top-level items to check the "Trim parent items" option). After that, when an item is selected in the primary links, the contextual menu appears, showing only the subitems of the selected item. Drupal already allows contextual "secondary links" based on the primary links, but these secondary links are limited to a flat list of items. Menu Trim, on the other hand, can display complete menu subtrees.

This module can also be used in any menu to trim parents when reaching deep menu items. This can make deep menus more usable, and the breadcrumb will still show the full path.

This module provides two menu-based features: a sitemap page and a jump menu.

First, this module provides a nested unordered list representation of a complete Drupal menu structure. menutree/1 provides a tree representation of menu 1, menutree/2 provides a tree representation of menu 2, etc. If no ID is specified, the primary_links menu is used. That allows it to be used as a simple menu-based sitemap, give or take a path alias.

Second, it provides a block for each menu in the system that provides a "jump menu". A jump menu is a select box of a menu from which users can select any menu item to be redirected straight to that page. (Drupal 5 version only)

This module was developed by Palantir.net

The Message Effects module adds attention getting JavaScript effects to Drupal messages (you know... the messages that say things like "This content was saved." or "You have an error.", etc -- usually above the content on your Drupal site). I have found that many users tend to miss these messages on the page, so Message Effects gives them a little "pizazz" to make them more noticeable.

This module depends on the JQuery Interface module which in turn relies on the JQuery Update module, so you'll want to download those too.

Administrators can choose between various effects selectable for status or error messages. The current list is:

• Pulsate - flash in and out
• Highlight - (the fade yellow technique) add a highlight background color to element and fade it away
• Shake - shake the element horizontally a number of times
• None - do nothing

This is a simple messenger module (ajax).
It allows registered, active users to send messages to on-line and/or off-line users.

Features
1) Messenger page with a textarea field.
2) Html messages are allowed (default filter).
3) Messenger block with a text field for sending quick messages.
4) Blinking text (can be disabled from the css) if the current user received a new message.
5) Messages are grouped into the 'unread' and 'archive' message types.
6) Complex css. The messages headers/bodies, notify/alert messages, blinking, ... are fully customizable from the messenger.css file.

Note
Disable the messenger for the TinyMCE ('edit-messenger-*' textarea) and FCKEditor ('messenger' and 'messenger/*' lines) WYSIWYG editors because it doesn't work with them.

Upgrade
a) disable the messenger module first because of the menu_hook() is changed
b) refresh your browser because of javascript changes

This module allows you to set some meta tags for each node, view or panels page.

Giving more attention to the important keywords and/or description on some of your nodes allows you to get better search engine positioning (given that you really only provide the keywords which exist in the node body itself, and do not try to lie).

The module may also be known under following names: nodewords or node (key)words. Meta tags is the preferred name.

Build scores for nodes based on the results of metrics functions.

This module was originally created as a 2007 Google Summer of Code project.

Basically you can think of this project as "making drupal easier by making more stuff nodes".

• Every microcontent entry is a node.
• Every microcontent entry is available as a block
• You can also choose "special" microcontent subtypes. For now:
  • site summary (site title, site body)
  • mission (mission title, short mission, long mission)
  • site details (footer)

So the basic site setup is done in your content area.
Blocks are made and moderared trough our famous content user interfaces.

Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.

This module is similar to the idea of CCK, but rather than allow the creation of custom content types, the module allows the development of set microformats such as hCard and hCalendar, with scope for the addition of other content types.

This project is still currently in an alpha stage, with a design of the database required first. Input will include JS elements such as a pickable calendar, and output will be both in XHTML format for display, as well as XHTML that can be copied and pasted.

Current Working Modules

• MicroID Module - Dynamicly generates a MicroID hash from a node authors email and the URL of the node. This module then generates a meta tag with the MicroID, and using jQuery also add's the MicroID to the node's class.

This module provides a simple "microsummary" of a Drupal site.

See Mozilla Wiki about Microsummaries for details on possible uses.

This module currently provides three microsummaries by default and can be extended with custom microsummaries about a site.

Possible uses include providing a count of new or total users, a count of total nodes on a site, a count of certain kinds of content added to the site, the name of the most recent user: anything that changes on a semi regular basis.

This is a Mime Mail component module (for use by other modules).

• It permits users to recieve HTML email and can be used by other modules. The mail functionality accepts an HTML message body, mime-endcodes it and sends it.
• If the HTML has embedded graphics, these graphics are MIME-encoded and included as a message attachment.
• Adopts your site's style by automatically including your theme's stylesheet files in a themeable HTML message format
• If the recipient's preference is available and they prefer plaintext, the HTML will be converted to plain text and sent as-is. Otherwise, the email will be sent in themeable HTML with a plaintext alternative.

This module is required by the Send module.

This project is based on work efforts by Robert Castelo, Gerhard Killesreiter and Allie Micka

MiniMenus is a module designed to provide Google-like registration and login links in the top right corner of a Drupal website for anonymous users, and a mini-control-panel for authenticated users and administrators.

MiniMenus integrates with the Administration (only in the Drupal 4.7.x version) and Masquerade modules if they are installed and enabled.

MiniMenus development has been sponsored by http://civicspacelabs.org/ . After May 10, 2007 the module has been maintained by Robin Monks.

The minutes module allows you to attach minutes to any event (as defined by event.module). Minutes "inherit" the categories of their parent event. They also allow you to track who attended the event.

Mobile Media Blog allows you to post media via e-mail or mobile phone.
It integrates with Mailhandler [1] and saves the submitted text as node and attaches all files sent with it.

In conjunction with image module and/or audio module it may be configured to directly post image or audio nodes.

You may choose to use the inline module [2] to display attached files automatically.
The mailalias module [3] allows your users to provide more than on e-mail address for posting.

Sponsored by erdfisch :: internetlösungen - http://erdfisch.de/

[1] http://drupal.org/project/mailhandler
[2] http://drupal.org/project/inline
[3] http://drupal.org/project/mailalias

mobit (MobilizeIt or MobileTheme) is a module that allows users to choose a theme for use with mobile devices. It has 2 parts. Part one allows the administrator to define one or more
of the installed themes as themes appropriate for use with mobile devices, meaning not many images, no
javascript and a simple layout.

Among those themes the user is able to select a theme as his mobile theme. Whenever the user accesses the site with a mobile device (identified by the UA profile) this mobile theme will be used. So the user default theme for web access will not change and the web-browsing experience will be as good as usual.

I like to share this module to get some feedback and new ideas for enhancements. As mobile devices get more and more popular I think this is an interesting area for enhancements.

The code allows to switch to on access to an external rendering system.

This module allows you to administer mod_auth_mysql apache users and groups from within drupal. Requires apache/mod_auth_mysql. More information on that module is here: http://modauthmysql.sourceforge.net/CONFIGURE

This module logs the modifications of nodes and comments done by non-authors (that is, anyone with the "administer content" or "administer comments" privileges) and displays the statistics on these modifications in a block as well as a detailed view of the modifications on separate pages.

Provides an administrative interface for managing content in moderation.

Allows you to preview content, as well as approve or deny, and send messages to the author informing them of your choice.

A module which auto-generates a skeleton or "scaffolding" for a module, along with hints on how to fill them in. Useful for newbie developers to learn how hooks work, and seasoned developers who are too lazy to look up what arguments a function has to take. ;)

通过管理页面就可以下载并安装模块，再也不需要下载、解压、上传等等麻烦的步骤了。
安全小组提示: 这个模块应该用于本地测试。

安裝此模組後，只要在管理介面輸入想要安裝的模組的檔案網址，就可以直接下載並安裝模組。

Allows modules to be downloaded and installed from the administration area.

Please note that this module is brand spanking new and may eat your babies. Help with testing mucho appreciated.

Note from security team: this module should only be tested on localhost.

Drupal assigns each module a weight. For most operations involving any module that defines a particular hook, the modules are invoked in order first by weight, then by name. This module adds a weight column to the module administration page, allowing weights to be viewed and edited.

Notice: There is a potential permission problem with this module that has not been solved yet. If you do not have root access or the ability to change file permissions you may not be able to edit or delete modules installed with this module. It is recommended that you do not use this module on a site you do not have full control over (such as a shared hosting account.)

Allows users to install modules and view documentation files via a web interface. This module aims to be platform-independent and have few dependencies.

Features:

• Install modules to current site or all sites
• View documentation for installed modules
• Ability to assign permissions for each option

Description

This module defines the "money" CCK field. It uses the Currency API, which is included in the Currency module, to get a list of valid currencies.

Only amounts with 2 decimals can be used. Any decimal separator and any digit group separator can be used, but it defaults to the comma and the dot respectively, which is according to ISO 31-0. The separators can be changed at any point, only integers are stored in the database.

If you only want a drop down field for currency then you might want to take a look at owahab's CCK Currency module.

Dependencies

• CCK
• Currency API

Sponsor

Etienne Leers of http://creditcalc.biz/.

Author

Wim Leers

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

This module defines a Views style plugin, so that if you have a view sorted first by a date field, you can show them grouped by month.

Construct monthly archive lists and blocks.

Notice: you should configure the block after enabling the module.

In versions for Drupal 4.6 and 4.7, delete the more_language folder if you don't need the Spanish or Chinese translations to avoid conflict.

This module is not ready for real use

We're waiting on a patch to moodle 1.8 to allow delegation of logout urls.

watch this space.

What is moodle?

Moodle is a course management system (CMS) - a free, Open Source software package designed using sound pedagogical principles, to help educators create effective online learning communities.

Moodle has a large and diverse user community with over 150,000 registered users on this site alone, speaking over 75 languages in over 160 countries.

How this module works

Drupal module that sets a shared cookie, and maintains a database that moodle can read.
Uses moodle lazy account creation.

Why create this module?

This module was developed for Linuxchix.org courses integration - released under GPL to make the world a better place.

Who should use this module?

If wish to create a drupal website / portal, and also have moodle handle the education/course portion. Theme the moodle instance the same and your drupal, and they appear to seamlessly integrate.

Allows administrators to add custom help messages to any section of the site.

The moviedb module provides the tools to maintain a large movie database.

The module treats movies, people (actors, directors...) and companies as separate nodes. This allows a great flexibility and extensibility.

The movies module allows the administrator to create, edit, update and delete movies in a database (including the IMDB link if desired), at admin/movies. They also have the ability to add movies (in the same fashion) to a movie wishlist, checking off movies from that last as they are purchased, automatically adding that movie to their main movie list, at admin/movies/wishlist. There is also a page which will find any conflict between the two lists.

For the visitor of the site, they can visit http://%your-site/%movies or http://%your-site/%movies/wishlist to view each of these lists, with the movie name linking to the imdb page, where applicable.

Movino is a collection of open source applications for streaming and broadcasting live video from smartphones. The main applications are the following:

• A client for Symbian Series 60 smartphones
• A client for J2ME capable camera phones
• A GUI application and a QuickTime component for OS X
• A video server for Linux
• A Drupal based web interface

More info at http://www.movino.org/

The Movino web interface

The following modules are bundled in this package:

讓使用者在你的網站上，透過瀏覽器以 webcam 直接拍攝相片，儲存在網站的相簿裡，並可以區塊呈現。還可與回應功能結合，讓使用者在回應裡留下照片。使用者必須安裝 flash plugin，並允許瀏覽器使用 webcam。

示範： http://www.bonvga.net/mugshot_galerie_photo

The Mugshot module enables the users to take directly a photo in web page via a webcam. The photos are then presented in a gallery or on a block.

The Multiforms module is designed for the collection of data from users. It can be used to easily author multi-page forms which are published as nodes. The data collected by the forms can then be exported. It was originally designed to handle contest and survey creation needs for the website of The Georgia Straight (http://www.straight.com/), a weekly Vancouver newspaper.

New: Support for the actions module has been added: submitting multiforms, or individual multiform sections, can now trigger actions. If already using Multiforms, you may have to run Drupal's updater to update your database.

This is a module which allows you to span one site across multiple domains.

You can configure which domains to use for different parts of your site including which protocol that section uses. It can also be used to put the ecommerce or user account functionality behind https, for instance.

This module was primarily developed for Oasis Magazine for the purpose of hosting different types of content, on different sites, while using the same database, so that information can be cleanly promoted between the different sites, without having to worry about syndication and the like.

This module requires the single sign-on module, to allow you to be logged into multiple domains at the same time.

A small patch to Drupal core is required for this module to work. It is included in the package.

This module defines a widget to be used with the nodereference CCK field type. It allows the user to select multiple items in an easy way. It consists of two lists, one of unselected items, the other of selected items. The user can select an item by moving it from the unselected list to the selected list.

Allows creation of new drupal sites from a central drupal site without the creator having access to database info. The new site is installed either in the same database with a different prefix or if the drupal db_user has access to create a database and grant privileges, then possibly there.

It has become clear to me that this module will be too proprietary to be of much use to anyone other than my specific project. I've uploaded the latest version, you're welcome to examine and use it if you like. There will be no official releases of this module.

The Multivendor Multigateway (MVMG) payment module strives to provide a shopping environment where registered users can all be vendors. The system uses some features from the eCommerce API and provides some stuff on its own (user-specific paypal settings for example).

THIS MODULE IS NOT EVEN BETA. USE AT YOUR OWN RISK

This module provides simple and hassle-free integration with MyBlogLog services. MyBlogLog provides community-based services and statistics to web sites (not just bloggers.) Think "MySpace"-like community features but you get to provide them on your site.

類似 My Yahoo!的個人化資訊頁模組，可以讓使用者建立一個頁面，裡面的內容除了來自該網站，也可以選擇 RSS aggregator 裡的內容。可收錄的內容包括：

• RSS aggregator 個別的 RSS feed。
• RSS aggregator 的 RSS 分類。
• 網站使用者的部落格文章。
• 手冊頁面。
• 討論區主題。
• 分類文章。
• 自訂內容區塊。
• 提供 API 讓其他模組可以支援。

MySite pages let users create a personalized summary of the site. The MySite module duplicates the functionality of tools like MyYahoo! and Google's personalized homepage.

The module allows registered site users to create a MySite page that contains content from throughout the site. For sites that use the Aggregator module, users may also add feeds from external web sites to their MySite pages.

In 5.x.2 versions, users with JavaScript can drag, drop and sort content on their custom personal layout. The 5.x.2 series also supports Blocks, Views and 'Droplets' -- content widgets created by the site administrator.

MySite 5.x.2.8 released 22-AUG-2007 -- bugfix upgrade recommended for all users.

MySite was written using an API/Plug-In model that allows the core module to be extended to handle additional content types. These content types do not have to be nodes.

Users group is http://groups.drupal.org/mysite and includes a development roadmap.

Developer API is online at http://therickards.com/api

Demo is online at http://therickards.com/mysite

MySite is sponsored by Morris DigitalWorks.