Extend and customize Drupal functionality with contributed modules. If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
Etsy Shop API
The Etsy Shop API module provides a wrapper for Etsy.com's API. You can use this to create a Drupal front-end to your Etsy shop, or simply create blocks showing some items from your shop's listings.
Use of this module requires an API key from developer.etsy.com.
Etsy has recently announced version 2 of their API. I will be updating the module to use the new API before an official release of this module.
Project Roadmap
These are some of the ideas I have for development of this project. If you have other ideas for useful features, I am happy to hear from you. File an issue to share your idea.
- Code re-write using new Etsy API
- Views integration
The former location of Better Exposed Filters
The Better Exposed Filters project page has moved
Drush users were having problems due to naming inconsistencies between the project name (Better Exposed Filters) and the project URL (bef). In order to fix that, the project page for Better Exposed Filters has moved here:
My apologies for the confusion...
Licensing Ecommerce
This module allows associating certain ecommerce products with the Licensing module.
At the moment, the workflow is very basic.
- When creating the product, you mark it as 'licensed' in the product settings fieldset.
- Configure the workflow status you want the transaction to reach before sending the email with the license keys
- When your customers purchase that product, once it reaches the predetermined workflow status it will send an email with all of the license keys for each product, and further instructions.
As of alpha 2, the email notification is customizable.
As time goes on I will be improving the configuration options and making it more stable.
Sermons
The Sermons project is a way to provide a sermon structure for your Drupal church website. It includes a number of ways to explore your churches sermons and allows your shut-ins and traveling attenders to stay in touch with the sermons.
Your sermons may have images, notes and sermon series tracked on them. You may choose not to use these options and they may simply not be used when creating the them for your website or marked as exclude on the Content Type display page.
Installation
A number of modules are required including CCK, Views, FFPC, FileField, ImageField, ImageCache, SWFTools. You will also need to install the one-pixel flash media player. Documentation on this may be found in the Adding support for media players of the SWFTools installation documentation.
This code is built for use with the Drupal Feature module. Consequently, that module must be installed and you will enable this feature according to the documentation. There is also a relevant screencast of Features called Making and Using Features in Drupal.
Compatibility Note: SWF Tools version 2 is required. SWF Tools version 3 is not currently supported. I hope to see this change in the future. A patch will be gladly accepted.
Point Board
Point Board
It is a simple module to get ability for your visitors leave
a link to their site with picture. Also your can collect all
your best links with picture in one block - Point Board.
It looks like a grid of pictures where you collect links.
To get the module installed and working please do the following things:
1. Download and install all depend modules: JQuery UI, Imagecache, CCK.
2. Download and install Point Board module.
3. Goto setup page and adjust your settings.
Feature Updates
1. Payment system
2. More flexible settings
Churches Install Profile Modules
Custom code for the Drupal for Churches install profile. It will be downloaded automatically as part of the distribution. There is little use for this code outside of the distribution. Issues related to these modules should be posted via the Drupal for Churches issue tracker
PowerAdmin
PowerAdmin is a Drupal module that provides API and a GUI to administer the configuration of a PowerDNS Name Server, with MySQL/PostgreSQL backend.
This project is sponsored by 2V S.r.l.
WARNING! Although things seems to start working, the code is yet too young to be safely used to administer a DNS!
Features
- Domain management
- Support for editing the domain SOA in a more friendly way
- Insert the TTLs as suffixed human-readable strings [TODO]
- Auto-append the domain name to records [TODO]
- Records management, as single entries or directly in a table form
- SOA record serial auto-update [TODO]
- PowerDNS configuration file auto-generation (with table prefix support)
- Supermasters management [TODO]
- Advanced ACLs: global, per-zone and per-record [future]
- Integration with AEgir to autoconfigure domains [future]
- Suport for zone templates [future]
Links
Stats
Stats provides an API for creation, calculation and storage of statistic values.
Basic features:
- Central definition of Stats types via
hook_stats_info() - instant calculation with
stats_run() - Views implementation
- Storage in different (custom) tables
- Different default calculation modes like COUNT, SUM, MIN, MAX
- Extendible by more calculation and storage modes by custom callbacks (e.g. for possible memcache integration)
- Functionality can be overriden by new stats-worker classes. (Default impementation: stats_default_worker)
Implemented contrib modules:
- stats_queue - queue calculation of stats, ability to enter an execution time - (dependency on Drupal Queue)
- stats_nodecount - counts nodes per user and per term.
The heavy-development source code is currently available on a github repository.
Contributed modules to use this API:
- Results (http://drupal.org/project/results)
Geoparser
A module to provide a common interface for geoparsing services such as Yahoo!'s Placemaker and various CCK fields.
Geoparsing?
Geoparsing is the process by which structured geographic locations and their identifiers (eg placenames, lat-long coordinates) are extracted from unstructured content, such as a blog post. Different techniques are used by various providers of geoparsing services, but broadly speaking the process is to identify placenames within the text, identify the context in which the placename exists within the text and then lookup the placename in a database of placenames.
This module passes a node's content to a geoparsing service (provided by a geoparser service module.) and saving the structured information returned by the service into cck fields. The module can store coordinate, placename and place id information and provides a per-node-type configuration. It also provides functionality to bulk geoparse nodes and an action that can be triggered on node insert or update.
Installing and Configuration
- Install this module
- Install one or mode geoparser service modules
Features Clone (for Drush)
Features Clone is a Drush command that allows quick cloning of a Feature. It can be used to rename or fork (e.g. to start a new feature off of an existing one) a Feature installed on a Drupal site.
Usage
drush features-clone <src_featurename> <dst_featurname>
Arguments:
src_featurename - Required. Modulename (machine name) of the Feature to Clone.
dst_featurename - Required. Machine name of the new Feature created after cloning. Note: source feature must be installed and enabled on a Drupal instance that the drush command is run against.
Attention/Caution:
Module uses pretty straightforward search/replace technique so if the name of your feature is something non-unique and can match some other things in your codebase, unintended/unpleasant consequences may follow. Please name your features with unique names and as with any other change to codebase: backup, test, test again.
Installation
Please refer to the included INSTALL.txt for detailed installation instructions.
rfid_login
Want to amaze your friends?
Sick of logging into drupal the "old fashioned" way?
Think that RFID access would be cool?
Then this module is for you!
To login to drupal, simply swipe the RFID tag and a browser will be started (if required) and logged in instantly as your user.
This module was built to enable instant login for Point of Sale with the ERP module by StratosERP.
The rfid_login module utilises services and a user login for security, whilst still enabling amazing convenience.
Middleware client
A middleware client. This module is a client for middleware server module.
Middleware is used to establish XML-RPC based nearly realtime data exchange among any number of Drupal sites and external systems. Data can be replicated in many directions using different routes with different rules applied. Creations, updates and removals are separated. Pluggable connectors take care of system-specific implementations.
Already implemented features:
- Drupal 6.x users exchange
- Simple source/destination routing
- Data flow monitoring
- Basic token-based authorization
Partially implemented features / need more work:
- Drupal 6.x nodes/files exchange
- Administration interface
New York State Senate
This collection of Drupal modules powers the website of the New York State Senate and is available as-is for use and adaptation by anyone who wishes to build a public-facing website for government or other agencies.
Several of these are "glue" modules that are very specifically designed for the NY State Senate's content types and policy-driven needs. Some, however, provide functionality that may be very similar to what is needed by other websites.
Some NYSS modules have been released separately, where they have functionality that seems general enough in scope to be usable as-is on other Drupal websites. These include:
- OpenLegislation, which retrieves legislation information from the NYSS OpenLegislation search engine.
- Whitelist, an input filter that can be used to specify and limit outside domain names that can be referenced in content created on your website.
Some of the modules in this collection will be updated to more general-use versions in future releases. In the meantime, this is what we've got!
Context Menu API
Turned into a related API module that is more flexible. See: Node Reference Highlight
Church Community Builder
This project's goal is to create a solution for integrating Drupal with the Church Community Builder Church Management System (ChMS).
This project is in the planning phases. If you'd like to give input (ie. feature requests) or financial support contact Mustardseed Media
We are now accepting funding
Donate funding using this chipin page to help make this project happen. When the chipin amount is reached, development will begin. The development approach will be incremental, so once the base module is developed we will be adding features as time goes along.
The chipin here will fund the following features:
- Base Drupal/CCB integration for both Drupal 6 & Drupal 7
- The core work will basically get Drupal talking to the CCB database, doing core API integrations.
- The initial focus will be on user integration. User accounts from Church Community Builder will be integrated into the Drupal user database. This includes basic profile information as well as login and site access.
Once these features are complete, more will be added. Next stages will focus on event integration and registrations.
Visual Admin
This module aims to provide a graphical administration UI.
A way to achieve it will be to offer an API so that modules can install their own buttons.
Of course, this can also be achieved with Views or even manually, the point here is to have a standalone module dedicated to that and opened to other modules.
The project is at an early development state but is already usable.
Included features yet :
- create buttons
- create groups of buttons
- display the buttons
To come :
- API to allow other modules to create their own buttons (using hook_install)
- manage the buttons status
- graphical parent group setting using drag&drop
To come maybe :
- manage several administration UI
Node Gallery Display / jquery slideshows for node_gallery
This Module depends on the Node Gallery Module http://drupal.org/project/node_gallery. It will take over the display of the gallery landing page and show different jquery slideshows instead of the default list.
DEPENDENCIES
--------
Node Gallery http://drupal.org/project/node_gallery
FEATURES
--------
At the moment it supports the Ad Gallery, Easy Slider and the Galleriffic Photo Gallery.
It gives you a Tab on the User Account Page, user/%uid/galleries.
Provides a block for random images.
Provides a user selectable display when creating a gallery
INSTALLATION
------------
Upload the module folder (as is) to sites/all/modules
Enable the module ( administer > Site configuration > Modules list ) in the node gallery subsection.
( Node Gallery Slideshow Integration )
USE
---
Slideshow or display control:
On the (create gallery) or (gallery edit) page there is a field set
called "Node Gallery Display Settings" with four options.
Make a selection to display the gallery as desired.
* Default Node Gallery.
(Thumbnails that open a photo gallery with Prev|Next navigation links.)
* AD Gallery.
(Photo display with thumbnails below. Prev|Next navigation, slideshow and slideshow transition selector.)
* Easy Slider Gallery.
(Single photo display with Prev|Next navigation links.)
* Galleriffic Photo Gallery.
FreeAgent API
This module will integrate Drupal with FreeAgent API.
The FreeAgent API provides secure programmatic access to the FreeAgent service, allowing you to build cool and useful tools and services on top.
OpenID connect
Bits and pieces that enable better OpenID connectivity.
May or may not be as envisioned by Chris Saad, Chris Messina.
http://chrissaad.wordpress.com/2008/12/08/proposal-openid-connect/
http://factoryjoe.com/blog/2010/01/04/openid-connect/
Strict filter for organic groups
Only show nodes and terms that belong to the active group.
What the module does and does not do
- The module removes terms and nodes from listings, menus etc.
- The module does not restrict access to nodes.
Also useful to make the forum module work with organic groups, or to make the forum module work as a feature with feature + context + spaces + og....
Instructions
Install and enable the module the normal way. This is all you have to do. The module doesn't have any permissions or any settings. It just filters away all nodes and terms that doesn't belong to the group you are visiting. If you don't want this filtering, just disable the module.
Please contribute reports on any issues.
Protocons icon library
Protocons is a clean and consistent collection of icons, buttons, glyphs and other graphic elements for building Drupal user interfaces.
This is not an actual module (yet?). It's a library of icons in 16, 24, 32 and 48px sizes.
Aim is to define the standard visual metaphors for Drupal concepts and actions.
The source SVG files contain multiple icons. This will probably change but works well for now.
Made with Inkscape 0.46:
http://www.inkscape.org
File naming and directory structure loosely based on the free desktop icon naming spec:
http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-lates...
Wordy
Wordy is the fastest, most reliable way of adding professional copy-editing to your Drupal site.
This module provides integration with the Wordy proofreading service.
When you add or edit a node you can choose to submit the contents of the node to wordy.com for proofreading.
Current development and maintenance is made possible in part by Peytz & Co.