Mohammed Sameer's Online Aggregator

Designed with the idea of making administrative tasks less cumbersome. Main feature is to break the module configuration up by Packages rather than having each module on a list with a field-set the packages are broken down into individual task pages to give the user a different way to locate and manage the site modules

A small module that allows image nodes that use both image module and imagefield module to become media entries in RSS feeds.

The OpenID client attribute exchange is a module designed to provide the core drupal openid module with the ability to do attribute exchange along with just simple registration for OpenID.

The module tries to be scalable and is currently in an alpha release since we have a lot to think about regarding hooks and how we can have the module extensible.

That modules integrates with Ubercart and Workflow-NG in order to proceed the printing of an order at checking out on a sitewide printer or per node related basis.

Example : Your website is a portal for some suppliers. A product is a node which is related to a given supplier. The visitor is filling is cart with some products from some given suppliers. The entity supplier has been built at using CCK and at editing this content type you can specify the printer parameters for this supplier. At checking out the part of the order concerning each supplier will be sent to his printer.

Some other uses may be found, as to simply print order and not only send email about them.

The module depends on : Workflow-ng - Ubercart Product - Ubercart Order
The module may require : CCK

A sub-module to format the order in a suitable way for Citizen Ct-S310 (Point of sale printer) is provided and may fit for other POS printers.

See README.txt in the archive.

Profile Complete Percent (PCP) is a dependency of the Profile module in core. It allows administrators who have access to use the module the ability to tag created profile fields as items needed for a user to be 100% complete when filling out their profile information.

A block is created which can be placed anywhere on the site that by default displays the current logged in user's profile complete percent. As the user fills out more of their profile, the percent increases. Additionally, a "next" tip link is displayed informing the user that if they fill out a particular field in their profile, they will increase their profile complete percent to a specific value. A link is provided for this "next" tip, sending the user to the exact page and highlighting the exact field that they need to fill out to increase their profile percent.

This project aims to create a web interface to create and control virtual private servers using Libvirt library. It's currently in Alpha development state and no code is released yet.

If you came to this page looking only for our feature rich taxonomy browser and widget 'cdm_taxontree' you can skip some paragraphs below in order to jump right to this module.

The module 'cdm_dataportal' is an biodiversity informatics application for web publication of most data relevant for this domain of information. It is in fact a set of four modules 'cdm_api', 'cdm_portal', 'cdm_taxontree' and 'cdm_mediauri'. Together they enable Drupal to search, browse and display the biodiversity data hosted by a CDM (Common Data Model, see below) driven data store. The resulting pages of this "DataPortal" partially mimic the layout of common taxonomic books.

The 'cdm_dataportal' module set is being developed by the Botanic Garden & Botanical Museum Berlin for the European joint project EDIT (European Distributed Institute for Taxonomy). One of the major aims of EDIT is to develop a platform for biological taxonomists, covering most biodiversity related data realms. This platform for cybertaxonomy is in fact a set of distinct tools embedded into a service driven architecture. The very core of the platform is the so called Common Data Model (CDM) which integrates all relevant quasi data standards. A CDM library is being developed to provide service layers to access and modify the data stored in CDM stores. The CDM library also provides the REST service application to which the "DataPortal" connects in order to fetch data from the CDM store.

read more

This is a very simple module that adds a 'weight' field to the tables already
used by the excellent Flag module.

http://drupal.org/handbook/modules/flag

This weight can then be used to provide sorting of flagged items. This module
also provides a Views field which can be used to sort flagged items. One
interesting use of this ability is to integrate with Draggable Views to create a
user-sortable list of flagged items (however this currently requires extending
that module to support non-CCK sort fields, and a custom save method).

http://drupal.org/project/draggableviews

This module is a simple event with participants implementation.

Simply, it adds a participant list on each node which is posted in an OG group, and whose type is configured as an Event node. Each group member can add or remove himself to the participant list.

Further, node owner can configure simple features, like whether or not group members can edit node, add themselves as participant, and if they can enter a role they want to assume for the event.
Misc UI options are editable through Drupal administrations pages, if participant list is displayed into the node, or as a tab on full node view, etc..

This module uses OG and Event modules.

Note: a Drupal 6 branch will be created soon.

For quite a long time, Drupal has had several "friends APIs". Buddylist, Buddylist2, Friend, Ajax Friend, User Relationships, FriendList, etc.

Don't use this module yet. This is a pre-pre-alpha-pre-pre IDEA. Right now, please only get involved if you are developing a Friend-like module

This made it _really_ hard for module developers to just ask: "are user A and user B friends...?" Each module had a different way of answering that question, and with different outcomes.

This API is meant to be the answer to this problem.

It provides a general API which answers the most important questions about user relations. Who are user A's friends? Is user A friends with User B? What elation types are available?

Right now, the API interfaces with FriendList as a demonstration. However, it has a _simple_ plugin architecture, so that any API can be used.

This module makes it possible for Courier-MTA to authenticate against a Drupal user database.

To do this:

1. Unpack into sites/all/modules directory.
2. Enable this module.
3. Read the README.txt file included with the module.

Tabs component for the GUI project.

Example:
$example =& gui_get_component('tabs');
$example->add_tab('Tab 1', 'I am tab content');
$example->add_tab('Tab 2', 'I am tab content');
$example->add_tab('Tab 3', 'I am tab content');
$example->add_tab('Tab 4', 'I am tab content');
$example->options['selected'] = 1;

print $example->render();

Developed and sponsored by Victoria British Columbia Web Design

Provides methods for other modules to use with translated content.

In particular, facilitates response to change in source translation, useful for modules that track data by the "source translation" (node.tnid value).

read more

The Book Post module makes it easy to post information about books. Any 10 or 13-digit ISBN placed between double curly braces {{}} in a post will convert into the book cover, title, author and publication info. All data comes from the Open Library Project, an open source catalog that allows users to add books and edit metadata. If there is no cover available for the book you want to post, go on the Open Library and add one!

It is also possible to use the Open Library ID number instead of the ISBN (e.g. OL8378495M). The Open Library has fulltext available for many titles in the public domain. A "Read Online" link will automatically appear in your post if the fulltext is available from the Open Library.

There are also options to include links to WorldCat, LibraryThing, and Google Books for books that you post.

This module is based on John Miedema's OpenBook Plugin for WordPress.

Formnode is a simple module that allow site administrators to render nodes into forms as HTML markup. You can select a node, the form where to render the node, and the weight to position the renderered node wherever you want.

It provide a simple and intuitive UI, using form_collect and form_store modules if they are enabled on the site. Else it provide an old and unusable UI :) Those last two modules can be disabled after site configuration is done.

This module has been originaly created by Makina-Corpus.

Note: a Drupal 6 branch will be created soon.

The Mailfix module allows administrators to provide email accounts to regular Drupal accounts.

For this module to work you must have previously installed and configured Postfix 2.1 or greater. A step-by-step installation guide for an Ubuntu 8.02 server will be available soon at http://howtoforge.net.

Once your Postfix server is appropriately configured you may install this Drupal module.

Domain settings (admin/settings/mailfix):

• You can manage multiple domains for mail delivery
• Per domain default quota (default is 100 MB)

User settings:

• Drupal and mail accounts share the same password, thus allowing users to manage their credentials from a single location.
• Users can access their mailbox using POP3, POP3S, IMAP and IMAPS
• Individual quota support for mailbox
• Mail forwarding (very useful for disabled accounts)
• Silent BCC monitoring of specified accounts

Future features:

• Auto-responder (vacation, temporary leave)
• More translation files

Users with "administer users" privileges can configure individual settings, such as mail quota, automatic forwarding, outgoing and incoming BCC.

Users with "administer site configuration" privileges can manage domains.

read more

Allow non-admin users on your site to create new users. The module automatically sends an invite email to new users with login information.

This module integrates with OG. This means that users can create new users in a particular group.

Drupal 5 only for now.

This module is dedicated to Jeff Miccolis.

Broken Anchor is a tool to find various errors in contents. Primary targets was to discover broken links in node bodies. Now it's also checking comments and clear email addresses.

The module is based on a cron job in order to check, once at a time, a variable number of contents (nodes, comments for now). Each content is prepared using Drupal filters (Input Formats) in order to check the same content version as displayed.

The module comes with a report view from where it is possible to check again, edit content or ignore the error.

Content discovering is based on a kind of API allowing to extend content types able to be checked.

The shared email module overrides the 'user' module's validation that prevents the same email address being used by more than one user. Works for both registration and account updates. Displays a warning to the user that they are using a shared email.

Based on http://drupal.org/node/15578#comment-249157

All this module does is modify the email address before it is validated by the user module.
Because it only changes the edit value rather than the form value, the validation will pass but the original unchanged email is still stored properly.

Confer a role to a user once they have completed specified requirements.

read more

This module allows users to batch-arrange existing nodes into a menu structure. Modules like Node Import allow you to easily add large amounts of content to your Drupal site. This module goes hand-in-hand with Node Import by allowing you to upload a CSV file that tells Drupal how all these nodes should be organized. This can be very useful for quickly "scaffolding" a site by setting up primary navigation menus.

For an example of the file format, assume you have several nodes that you want arranged like so:

Node1
- Node2
- Node3
-- Node4
Node5
- Node6
Node7

Your CSV file would look like this:
Node1, ,
, Node2,
, Node3,
, ,Node4
Node5, ,
, Node6,
Node7

When you upload the CSV file you can select whether you would like this structure added to the Primary Links menu or a new menu.

This module provides functionality for the creation of Dynamic Images to be used in place of textual buttons or titles where necessary in a theme.

The real advantage of this module is with sites that use Localization and Internationalization. Having dynamically created graphics, cached and loaded where it might usually be done via CSS or IMG loads, greatly enhances the administration of multiple text-driven graphics without having to manually create them in a program like Photoshop or any graphic editor for that matter.

This module was born out of necessity to add administrative flexibility to webmasters without need for graphic design work, uploading of images to the server and manipulation of code to add said graphics to site.

View Sort sorts the field and filter options when creating or editing views.

This is a very simple module, but it could easily be extended to offer different sorting algorithms or to sort any form option list.

The Comment Permissions module enables control of commenting by user role and by node type. Additional user permissions for selected node types are added to the user access system so you can configure commenting with more control than Drupal core provides.

Note that "reply" links below comments may still appear for users without the permission to add comments. This is unfortunate, but I haven't found a workaround. See http://drupal.org/node/185855 for more information. Of course, the links can easily be removed in the theme layer.

Drupal 5 doesnt have a nice easy way for module developers to drop .tpl.php files in their module directories for use with modules that do a lot of output. I have no idea why. Drupal 6 has this but 5 does not. So I've created a module that allows module users to mimic the features of drupal 6 without the need to modify drupal 5 core files. It's not identical or perfect but its about as close as you can get without actually upgrading to 6 which may not be a path you can take because maybe some of your modules dont have a D6 version. Also, this system doesnt lock you into a '$content' variable like the normal drupal page template does. It allows you to create the '$content' using the $vars variable. $vars is an array that contains values that come straight from your module. There is also a custom_template.php file that allows themers to inject stuff into the $vars variable as well just like they would with drupal's template.php. Here's a small list of what this module allows you to do:

Create template files in your own Module directory (these can then be overridden by files of same name in current template dir as usual)
Send variable directly to a template (something not possible in d5 and I dont even think d6 does this either, though not sure on that).
New custom_template.php file for themers to use just like drupal's template.php

read more

More Like This provides a mechanism (and soon a framework) for providing related content. It currently supports an internal taxonomy search, but it will soon be opened up with a framework for plugging in morelikethis providers. This data is provided either as a block or as node properties to be manipulated during theming.

This initial release includes a taxonomy based lookup mechanism for More Like This content. It works by first
specifying your "Thumbprint" for a particular node on the node edit form. By thumbprint we mean you can specify
the terms/words that you, as an editor, feel uniquely identifies this content item. You can either select existing
taxonomy terms associated with this specific node, or enter free hand terms. When performing the lookup we will
determine what other nodes in the site match the provided More Like This terms and those with the highest
relevance/hit count will appear first in the list.

This initial release includes one type of search based on Taxonomy. Over the course of a few release we will
develop a pluggable architecture for search providers to integrate other mechanisms for finding related content.

read more

The autoload module is a utility module. It allows other modules to leverage PHP 5's class autoloading capabilities in a unified fashion. It does, naturally, require PHP 5.1.2 or later.

You do not need this module unless you are developing a module that makes use of classes or you are installing a module that depends on this one.

Drupal 7's integrated self-learning code registry is far better than this module anyway, so this module will never be ported to Drupal 7. Drupal 6 is the only version that will be supported, but the code conventions used by this module will make moving to Drupal 7 easier for class-using modules.

See the included README.txt file for information on how to use this module in your own modules.

This is NOT a module, this is a Ruby gem used to vastly increase Drupal development and productivity from the command line. This page will be used for issue tracking only.

Currently the following features are available:

• Module building wizard
• Todo list scanner

For installation or usage information visit http://vision-media.ca/resources/drupal/drupal-module-builder-gem

Developed by Victoria Drupal Development.

Field copy allows copying between fields for any content type. The fields must have the same type in order to copy.
Includes the option to nullify the source field.
Currently it requires CCK and it allows copying any cck field to any cck field of the same type ie. text, integer etc...

Provides API for the field_copy function.

Currently this module is considered alpha, so please backup your db before using this module.
In the future I will be adding undo functionality.

Even then you are strongly encouraged to back up your data for any module that alters your data.

Add pop-up tool tips to your content's text with this filter. 100% CSS, Tested on IE6,7 and FF2 -- need some feedback from others.

Enable Tool Tips in the Input Filter configure section of your default filter.
To use add [tip:Text to highlight=The tooltip's content] to your node body as many times as you like!

The problem: Dumping users onto the node/add page is ugly, especially if you have lots of node types and don't want to confuse users.

The solution: Postblock module. It exposes a simple, themeable sidebar block with links to just the node types you want, and hides any that the current user doesn't have permissions for.

That's it. That's all. Postblock!

It adds taxonomy terms to the menu system. This module depends on PathAuto if you are willing to build a proper hierarchy menu structure out of your taxonomy terms (if the taxonomy has hierarchy of course).

Some time ago I saw Taxonomy Menu which is similar and probably a lot more customizable, however, I didn't like the fact I should use some custom URL for building the taxonomy pages instead of using the standard ones, which get automatically created by pathauto.

With this module, you can configure it in a way to show each term as a menu entry and display it any menu parent of your choice, meaning that you can create a menu and have it being the parent of your taxonomy menues, and then, have them displayed on a separate block rather than on navigation.

It depends on pathauto in the way aliases are generated.

For instance, if you aliases are:

category/topic/drupal
category/topic/drupal/modules
category/topic/drupal/themes
category/topic/linux

You'll have a menu structure created:
-drupal
|_ modules
|_ themes
-linux

with those aliases.

Sponsored by
Infomagnet

Disable being able to re-use CCK fields (prevents splitting fields into separate tables when new fields are added to a content type). This is useful when custom modules have hard-coded SQL queries to CCK field tables where re-using a field would break the queries.

Current options are disable the submit button, remove the form, or prank the user to move the button around the screen on mouseover.

(Yet another) jQuery plugin module. This module aims to be a simple, lightweight, and easy to use jQuery plugin handler for Drupal 6.

If you have a module that is using a jQuery plugin, the usual reaction is to drop the plugin into the module directory and be done with it. However, this becomes a big problem when you have two different modules which use the same plugin. At minimum, the library will be included on the page (and downloaded by the browser) twice. At maximum, conflicting versions or multiple initializations of the same plugin can cause major problems for the page.

A plugin manager/handler will place all of your jQuery plugins in a central location so there is no duplication or conflict.

My frustration with the other jQuery plugin managers (such as JQ and Plugins) was that they required you to write a lot of PHP code just to have central access to a jQuery plugin. Each jQuery plugin got represented by a separate module and the overhead as compared to "just dropping it in my module directory" was frustrating.

To use JQP with your module or theme:

1. Enable the module.
2. Create a directory called "plugins" at sites/all/plugins or sites/[example.com]/plugins or similar.

read more

Implements a new form element named taxonomy_widget for selecting a vocabulary and then a term within that vocabulary. The term list is dynamically populated by jQuery when a vocabulary is selected.

read more

PDS is a generic tool for storing and retrieving key-value data pairs for a Drupal path.

This module adds administrative links to nodes and blocks for users with proper permissions to easily edit content. These links conveniently appear when the user mouses over a node or block, and then disappear on mouse out. Admin:hover also integrates with the Devel and Clone modules.

Check back soon for the Drupal 6 version!

The icons used by this module are from famfamfam's wonderful Silk Icon set.

This project is made possible by DPCI.

Pathtrack works with Drupal's statistics module to track the paths of visitors once they enter a specific page. It creates a report to show number of visitors and the paths they took. Also has an optional CSV output.

Note that this module is still in development. The dev branch is functional, but it's output may exceed your php execution time (usually 30 seconds), Depending on the number of days you want results for, or the number of visitors your site receives.

This module was generously sponsored by Gameface Web Design, a Drupal shop specializing in module development and Drupal theming

Contact Redirect add a redirect field when editing the site-wide contact forms provided by the core contact.module. It allows users to easily redirect visitors to a thank you page or to more information for each contact form. The default is still the homepage.

This module was generously sponsored by Gameface Web Design, a Drupal shop specializing in module development and Drupal theming

FeedAPI Comments is a FeedAPI add-on for aggregating comments to your site.

It consists of a parser that pulls comments from a remote site and a processor that creates Drupal comments from it. You can alternatively use FeedAPI's node processor which allows you to create nodes from remote comments.

Currently supported sites:

• vimeo.com

Additional sites can be implemented by following the example of feedapi_comments/parser_comments/sites/vimeo.inc.

A repository viewer for Drupal, building on the Version Control API. This builds on the unstable, unreleased 2.x branch of Version Control API, so it will break in horrible ways and eat your children. (Won't be backported to Version Control API 1.x because the API doesn't support this functionality there. In fact, I'm building up the required functionality in tandem with this module, don't even think about a backport.)

Repoview only works with VCS backends supporting direct repository access, which is only the Subversion backend at the time of writing. Oh, and have I mentioned that the functionality is currently *very* incomplete and not usable for the public? No? Ok, then that's sorted out now. Don't download this (yet) unless you want to help with development - which would in fact be highly appreciated.

OpenID Simple Registation (SREG) is an extension to the OpenID Authentication protocol that allows for very light-weight profile exchange. It is designed to pass eight commonly requested pieces of information when an End User goes to register a new account with a web service.

This module implements the complete specifications. For this purpose it extends the Drupal core openid.module for the Consumer part and the openid_provider.module [1] for the Provider part of the specification.

Using OpenID Simple Registration Extension 1.1 - Draft 1 [2]

read more

This module provides an API for using the flot graphing library.

More information about flot is available here http://code.google.com/p/flot/

Addresses Extras is a set of extensions to the Addresses module.

The idea is to make it useful by having many different type of data attached to a user. A complete profile, and for some fields with functionality that is not found in the base Addresses module.

At this time, I am working on the following additions:

• Names (Alias, Person and Business)
• Notes (anything the user wants to write about himself or about a contact)
• Internal Info (fields only accessible to specified roles, usually for the admin(s) to control different aspect of users)

For myself, I put the URL where I can find info on how to deal with the Drupal CVS: http://drupal.org/handbook/cvs/quickstart -- this may even help others 8-)

These modules are sponsored by Made to Order Software Corp.

Allows user interaction among a trusted community of users to foster a more direct and personal exchange of ideas.

read more

This module is very simple with following feature -

- Provides a menu for multi site list
- List all sites by reading sites folder that is sitename as per drupal multisite instruction
- Provides link to run cron and update.php for all site from a single site

Post new feature/bug in project issue queue. Hope this will help you manage your sites in more better way.

This module helps to integrate osflv player in drupal.

Utilizes the tar program to archive files or directories, optionally presenting archives for download.

The uc_webform_productize module is designed to be paired with the webform_associate module. Currently the code is not working, but the objective is to create a uc product node that is paired with content types used by webform_associate. (working) This product should then be added to the cart each time a webform submission is created (not working). We will then need to devise a method of pairing submissions with transactions in a many to 1 relationship (not even sketched out).

Once we've done this we can go around the rough edges and make sure it's good to go, but paired with webform_associate, this module should go a long ways toward making event registration in Drupal quite simple.

Currently this is Drupal 6 only, I have no intention of doing this same dev for D5.

This module allows you to put products in your Übercart store on the auction block. Users will be able to place bids on the product until the auction expires. When it does, the user that placed the highest bid on the product will be able to add it to their cart and purchase it at the price they bid.

This module requires Ubercart 2, which is currently only available as a development release. A backport to Ubercart 1/Drupal 5 may be forthcoming, but do not hold your breath. For now, please use Ubercart 2 and Ubercart Auction for experimentation only.

Ubercart Auction is sponsored by Precision Intermedia. "Imagine no limits." Ubercart Auction was developed for Lost Coast Communications.