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.
Provides Drush commands for adding, updating, and deleting users from a CSV or JSON file. This allows you to quickly and easily create users, update their information, block users, and delete users, all by selecting a JSON or CSV data file.
Mimics the "select and print" WordPress module. (Credits to Mile51.com for the WordPress plugin. http://www.mile51.com/selectAndPrint.html)
Perfect for blog or recipe websites where you need to display an online grocery or ingredients list. Enter your list in the specified text format, and this module will turn it into checkboxes that your viewers can use to select and print a shopping list.
Provides a flexible text format that can be attached to any kind of content
Lists are entered using very simple formatting text
Example formatting that will be turned into the shopping list:
Foster Farms Split Chicken Breasts $.99lb
Pork Spareribs Buy 1 Get One Free=$3.49lb
Rotisserie Chicken 32oz. $4.98 when you buy 2 or more
Rib Eye Steak $8.99lb
Pork Center Cut Loin or Rib Chops $3.49lb
Clorox Bleach $1.67 each
Paper Towels 3 Big Rolls $2.99
Opti-Free Mulit Purpose Solution $8.99
Depend 14-18 ct. $11.99
Poise 36-72 ct. $11.99-Print $1 off Poise Coupon=$10.99
Excedrin 20-50ct $2.99-Use $.75 off Excedrin 7/10 SS=$2.24 each
Extension module for Views RSS that provides Content namespace and content:encoded item element.
Open Media Broadcast Schedule provides Drupal-side schedule integration for broadcast playback servers. It creates an airing content type, via features, that stores the current schedule. This module also provides bulk schedule update functionality that is used by OM Timeslot Scheduler as of the 7.x release.
This module is dependent on the 7.x branch of OM Playback Servers.
Open Media Broadcast Schedule takes a fundamentally different approach to broadcast schedule integration than OM Airing. This module integrates with broadcast playback servers via their API, which is exposed by OM Playback Servers. Originally this functionality was planned for OM Airing, but the maintainer of that module did not want to include API support. Thus the new module.
The Open Media Project will no longer utilize or provide support for the OM Airing module.
This module provides integration to Credit Guard Redirect Payment service.
The module's architecture allows one to use it as a bridge for multiple client modules working on the site in parallel (e.g. serving ubercart commerce as a payment method and in addition being used by a webform for donation means)
The main module provides the actual bridge to Credit Guard service while the sub-modules are the adaptors to the specific client module which consume the service.
This is not a Drupal module but an exported set of language-aware code templates to enhance Drupal development with the NetBeans IDE versions 7.0 and above.
Check out this short screencast for more information and a demonstration!
- Download and extract the file
- Open the Netbeans preferences dialog
- Click "Import" in the lower left-hand corner
- Select the "drupal-netbeans.zip" file from the downloaded package and click "OK"
- Select "OK" in the confirmation prompt. Don't worry, your existing config will remain intact, only code templates with the same names will be overwritten.
Similar to Drush, there is only one available download, the 7.x version, but it works for both Drupal 6 and 7.
Type the template name and press tab to insert it into the current file.
A full and up-to-date list of the templates provided can be found in the project's README.txt.
Are you missing a frequently used hook implementation? Have any other useful templates you'd like to add? Create an issue and, for bonus points, submit a patch! :)
There seems to be no unified library to simplify integrating with webserver softwares and their configuration files like .htaccess (Apache) web.config (IIS) etc. Which makes it almost impossible for Drupal developers to fully integrate with all the powerful features these webservers have to offer without having to be worried about differences, manually editing files, conflict with changes made by other modules and a safe way to keep these settings up-to-date with latest modules’ changes.
These module is an attempt to address all these issues and finally making proper integration with webservers possible.
In first version there will be no unified syntax since it’s not an easy thing to implement and requires good understanding of difference between popular web servers. However it will come with some very useful features:
- Module hook to introduce supported webservers , require webserver configs and define some indicators so webserver integration can check whether their changes is applied or not
- Module hook to alter webservice configuration file in text format (For example using regular expression). The running webservice will be send in as a parameter
- Hook for defining new configuration files in different locations (by default root and sites are already defined)
Provides a rough module for pulling database tables from a remote MSSQL server to a local MySQL server.
This was originally written to facilitate a migration from CandyPress to Drupal.
It may not be 100% perfect or complete, and it requires some work on the developers side to define the tables to import, but it should provide a starting point.
This module is under development. This module will not do anything out of the box. You will need to configure multiple settings and views to get this to function the way you want it to. To help, I have added a test example feature module.
Here is the goals:
- You are on a page listing content as a view(ie 'requested datasets'). Each content has a flag link.
- User clicks the link to flag the content. Page reloads. On the sidebar a draggableview block shows up.
- User flags 2 more items. Now there is a draggableview with 3 items. User can drag the items up and down
- Based on the order the user ranks the items the main view order changes.
Patch Flag Limit module - #1451536
Need to apply this patch to flag module #1596492: Flag database data not cleaned up on comment & node delete Patch #9. Without this the flag limit module will include deleted nodes and may produce undesired results.
This module extends the devel module's devel_generate to allow example forum structures to be generated.
Drupal core's forums (including those enhanced by Advanced Forum) are really just taxonomy terms, and the devel_generate module can generate taxonomy terms by itself.
What this module adds is the ability to create some terms which are forum containers, plus it also specifically inserts generated terms into the appropriate vocabulary.
Who should use it?
Developers might want to use it to create test data when working with core forum or Advanced Forum.
Similarly site builders could use it to create example data in order to evaluate Drupal's forum functionality, including enhancements to this functionality added by other contrib modules.
The forum_generate module adds an admin page to those already provided by devel_generate:
...hopefully the options there are self-explanatory.
If you want to create a set of test forum data, you might want to do something like:
- generate 100 users
- generate 5 forum containers and 25 forums
- generate 250 Forum topic nodes, with maximum 50 comments, adding taxonomy terms to each node.
This module provides minimal entity type that is fieldable with absolutely zero extraneous functionality.
Why would you want to use this when node module enables you to create as many custom content types as you want?
Downside that i find difficult to overcome with node entity is there are too many modules that depend on it and force added functionality that you don't always want, and it gets worse when you cannot disable the added functionality. What if you want to use a custom content type to store information that is not meant for public "content consumption"? too bad! you cant with node (or at least i found no easy way to prevent that). Your custom node type will appear in search results, have comments attached to it (minimal metadata when comments are disabled), etc etc etc. I didn't want any of that and was fed up with not being able to turn off unwanted extra functionality on node types, so i created this module to provide a way to create custom content types without any extraneous functionality, unless explicitly added via fields.
While module is currently in usable shape, it is not yet in optimal quality.
This is my first ever attempt at writing custom entity implementation and i am still learning.
In some servers I have not access to source control because of policies or whatever.
This drush script helps to create a 'package' that can be deployed to a server, containing only those files that must be overriden and a script for removing files that have been removed in source control between two tags, branches or revisions.
Download drush_release and put it on your drush/commands folder or symlink it there.
Execute drush release-patch tag-start tag-end folder-to-create.
Use the --tar option for creating a tarball folder-to-create.tar.
Use the --no-trunk option if drupal base directory is inside git repository base directory.
Use the --svn option if repository is svn instead of git.
Adds AJAX Block for Site Admins to approve pending user registrations.
A themeable fieldAPI field which invites authenticated users to 'agree' with the entity.
Agreer user ids are saved.
When the optional threshhold is reached, and email can be sent to all agreers and cron fires a hook.
This module helps manage different "editions" of the front page of your website. It is a Feature module that provides an "edition" node type which uses Panelizer so you can attach a panels display to the node. Each edition node represents a different "edition" of a panel so that content editors can layout a given edition while it is unpublished and then publish the edition when it's ready for display. This also includes support for a Node queue to determine which edition node should be displayed on the front page of the site, although edition nodes don't have to be used on the front page only. Since each is a node, you can trivially give them URL aliases and menu items and use them for various landing pages throughout the site.
This module enables Drupal sites to automatically upload files from supported CCK audio fields (FileField, AudioField, AudioRecorderField, PhoneRecorderField) to Soundcloud (http://soundcloud.com). It also provides a CCK formatter that makes it possible to select and play SoundCloud files as CCK fields.
The SoundCloud Tools module has been originally conceived and implemented by the MIT Center for Civic Media (http://civic.mit.edu/).
In the future common functionality of module that implement Google APIs can be pulled into this module.
Features this module provides:
- Drush support for quick download of library
About the project
This module is 3rd party integration with Tor (anonymity network).
You have to be Drupal developer to use this module.
Tor (short for The onion router) is a system intended to enable online anonymity. Tor client software routes Internet traffic through a worldwide volunteer network of servers to conceal a user's location or usage from anyone conducting network surveillance or traffic analysis. Using Tor makes it more difficult to trace Internet activity, including "visits to Web sites, online posts, instant messages and other communication forms", back to the user and is intended to protect users' personal freedom, privacy, and ability to conduct confidential business by keeping their internet activities from being monitored.
This module provides basic functionality for Tor project by implementing simple server connector.
If you need to implement additional functionality, patches are welcome.
1. Install module.
You need to have Tor server details to use this module.
Google+ History API integration & utils project aims to develop a simple layer for integrating Drupal objects and workflows with Google+ using the brand new Google+ History API.
- Simple authentication with a configurable API access key
- Client side flow (currently working on simple integration methods)
- Server side flow (Rules integration for submitting moments to the Google+ stream?)
Initially this project would be able to post simple activities in order to test the developer preview and experimenting the new API.
More details on next days.