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.
A module for importing a gedcom file and facilitating the display of a family tree on a personal web-site, using common tools like Views and Page Manager. The module is not intended for on-line creation or maintenance of genealogical data.
More info : http://www.tagnpin.com
tagNpin incentivizes your readers to invite their friends to check out your blog and will help you *engage* your current users with more repeat visits, Facebook likes and comments.
Key features for your readers:
* Readers connect to your loyalty program with Facebook.
* Readers earn loyalty points or badges for daily comments.
* Readers earn loyalty points or badges for Facebook likes.
* Readers earn loyalty points or badges for PlusOnes.
* Readers earn loyalty points or badges for Tweets.
* Readers compete to be at the top of your loyalty leaderboard.
* Readers redeem their points for quality gift cards and offers.
* Facebook loyalty app gets generated automatically on the go
Key features for you:
* Customize the rewards you offer.
* Keep track of recent and trending social actions on your blog.
* Keep track of actions taken by each reader and learn more about them.
1. Activate the plugin through the 'Modules' section in Drupal.
2. Visit your tagNpin options 'Configure' for to configure the settings
3. Get Secret Key and brandid as explained in the following steps
->Go to www.tagNpin.com and login (using information from registration)
->Click on Developer API from bottom left in sidemenu
->Click on API from menu displayed under 'Developer API'
->Click Authentication from there
A new widget for the body field that does not expose the 'Edit summary' link.
My content editors keept clicking that link thinking "what does this do?" On most content types, I want the automatic summary splitter to work it's magic anyway. Unfortunately, every content type has a body field already, and 'Long text with summary' fields in Drupal 7 don't let me change the widget to get rid of the link to 'edit summary'. (edit: but I think it may be a checkbox on the settings form?)
I wanted a widget instead, so, I wrote this.
Flag cart extends Flag. It allows to create block with cart icons that are automatically updated when content is flagged.
Go to 'admin/structure/flag_cart'. Here you can see a block settings for each flag created with the Flag module. In the block settings set the following:
- Cart url: Enter here the url of the flag (the view.
- Cart icon: Define here a custom cart icon for the block. It can be a local path or an url.
Tweaks for Wysiwyg capable editors (mainly CKEditor).
The 51Degrees.mobi mobile device detection plugin is a complete pack to help mobilize your website and blog.
It includes a mobile device detector and switcher to select themes based on the type of device visiting your website, a selection of mobile themes and an administration tool to allow easy, quick implementation.
- Mobile detection and switcher which automatically detects and switches between desktop / mobile theme, or the request can be redirected to another URL
- Easy to use administration tool to set-up and define redirection rules. The plugin can be downloaded and working within minutes. Rules can be defined to treat small screen mobile devices, smartphones and tablets differently.
- Detects over 11000 mobile device combinations and updated regularly. No cloud services, PHP extensions or external components are required. Once installed the detected device properties are also available to theme developers.
- Developed and supported by 51Degrees.mobi a leader in mobile device detection tools and used by over 220,000 servers and 500,000,000 devices per month. Additional detection capabilities including Tablet, Smartphone, Small Screen / Feature phones and additional themes are available from the 51Degrees.mobi website.
A way for those in some form of mental health/substance abuse therapy to "journal" (often at their therapists request) but not have to carry it around with them and will allow their therapist access to whichever entries the user chooses to allow. All access controlled through Drupal's user module.
presentation with HTML 5
This module will add an Author Relationship UserID to views under the Node group. This should help in advanced Views configurations. This drupal module is great for querying two different types of nodes both of which created by the same user.
Somerset Drupal User group
Just a test. Checking out Git on D.O.
Deletes users that have never logged in.
A module that allow blocks to be displayed in a popup modal. Works with webform blocks and custom blocks.
Activating the block within the block configuration settings area will hide it from normal display. For example display: none; and will display it in a popup modal instead.
This is a simple module adding Font-Awesome to drupal, and including minimal template preprocess function.
- Download font-awesome v2.0 from http://fortawesome.github.com/Font-Awesome/
- Extract the zip file and rename the folder to "font-awesome"
- place the folder inside of the following directory: sites/all/libraries
- Confirm that the css path is: sites/all/libraries/font-awesome/css/font-awesome.css
Enable this module, you should see the result.
Furthermore, themer can use theme_preprocess_HOOK function in template.php, to modify and add the icon class. Read the module code for detail.
Drupal automatically hides menu items for paths that are not accessible by the current visitor. This is often very useful, but occasionally it is preferable to show the menu item, and show an 'access denied' page after the user clicks on it.
Unfortunately, there is no such functionality in the Drupal core. This module aims to fill this gap. It adds a new form element titled 'Ignore access' to the menu link edit screen. To use it, one or more
of the roles should be selected. If a visitor has one of the selected roles the menu item will always be rendered, even if the current user has no access to it!
If a visitor clicks on such a link but has no access to it, the standard Drupal 'access denied' 403 page is shown.
Drupal has a very powerful image manipulation UI, so why write code when we can easily use that for any purpose?! The problem is we can't! The reason is image manipulation UI only accepts one argument which is the source image. All other parameters and options are static. For example if you want to put the source image behind a frame you can, but if you want to dynamically change frame's image you either have to make new preset/style for each different frame or write a custom special action.
Another example is rendering texts dynamically, you can pass any text you want to the image style and have it rendered without writing any custom action
This small module adresses this problem by letting you pass any argument to image module, parameters pass via query string
and you using them you can override any style parameters on the fly.
All you have to do is to use image_style_argument_url instead of image_style_url when generating the image url
For full documentation please read README.txt
$style_override = array('effects' => array(
9 => array ( //Overlay (watermark)
'data' => array (
'path' => 'public://my_frame.jpg'
image_style_argument_url('style_name', 'public://myimage.jpg', $style_override);
D7 petition system.
This is the start of a module to integrate Delivra's services into Drupal. The goal is eventually full API integration and administrative user interface to configure all aspects of Delivra's service to work within a Drupal site.
Delivra has made a change to their service since this module was started. They now allow all accounts to use their SOAP 1.1 based API. That opens the doors to a much more featured Drupal module.
I have started by building reports and in general working with their SOAP web service. Being it's a 1.1 SOAP interface there is some work to parse the responses in a more modern fashion as you can with SOAP 1.2. Next will be to integrate with Drupal Commerce for order tracking to support segmentation of the email list to power targeted marketing.
Clickstream JS is going to be postponed as the JS is not Drupal compliant.
Delivra is an enterprise grade Email Service Provider (ESP) that compares to companies like AWeber, iContact, Silverpop, etc.
Deprecated! I've move the code into the 7.x-1.x of: http://drupal.org/project/imagefield_tokens
Adds default values for core Image field Alt and Title attributes. Supports Tokens. D7 only.
User Request Name is just a small module that offers a way for users to retrieve their username when they forget it. It will send the user an email containing only their username after a user provides an email address.
All in one very simple field validation API module :
- Instant form validation and inline feedback through fast AJAX calls
- Integrated with Drupal's element_validation for forms
- Optional masked input in fields using the Masked Input Plugin
- Optional : hide all elements that were succesfully validated after submit for a better UX.
Available on https://github.com/DieterVanmoortel/fieldcheck
Mailhandler Mbox module provides a retrieval library that will be used to retrieve mbox file messages. That works with the Mailhandler module to parse the elements of mbox file emails as Feeds mapping sources when importing content with Feeds and Mailhandler.
Mbox is a generic term for a family of related file formats used for holding collections of electronic mail messages. All messages in an mbox mailbox are concatenated and stored as plain text in a single file. Mbox usually came from Mailman archives or others mails software.
Mbox related tools:
- Mailhandler - provide basic fetcher and parser.
- Pear: Mail_mimeDecode - Provides a class to deal with the decoding and interpreting of mime messages.
- Pear: Mail_Mbox - Read and modify Unix MBOXes.
- Enable all modules: Feeds, Mailhandler (and its dependencies) and the "Mailhandler Mbox" module.
- Create a new node type for the importer. For instance "Mbox repository". Each node of this type will hold each Feed importer configured later on. You could have a different set and/or repository per node, for instance.
EDIT: You only need this module if you are using release 2.11 of the openlayers javacript library.
Check the version you are using here: admin/structure/openlayers
In version 2.12 the problem with the google terms-of-service popup does not occur.
This small D7 module provides a block which when added to an OpenLayers map page will fix the issue described here: http://drupal.org/node/1540534.
Install and enable the module.
Go to Structure > Blocks (admin/structure/block).
Add the openlayers-google-popup-fix block to one of your regions.
You will normally configure the block to only appear on the same pages that your OpenLayers map appears on.
This module allows the easy and flexible querying of a Solr index trough Views. It is flexible enough to query any Solr schema just by providing the name of the fields.
It doesn’t do any indexing of content in a Drupal installation; it is just for those situations where you need to query and display results from Solr with the Views module.
Views row operations provides a new views field which allows you to add buttons to a view row that trigger operations on that row. It extends the power of Views bulk operations so that each button can be configured in a very similar way to bulk operations.
Rationale: Less is more
Views bulk operations is an awesome module, which is designed to allow operations to be applied in bulk to a view. It's user interface is well suited for this objective, but it is a bit long-winded when you just want to apply an operation to only one item in a view.
The purpose of this module therefore is simply to reduce the number of clicks a user needs to perform in order to execute a 'bulk' operation on only a single row. With Views bulk operations, this can take up to 4 clicks and some scrolling: For example, if your operations are in a select drop down:
- select the row, then scroll back to the top
- open the select drop down
- choose the operation
- then click 'Execute'.
If you're using buttons for your bulk operations, there are less clicks (2), but still potentially a bit of scrolling.
With Views row operations, a user can simply find the row in the view and click a button in the row to perform an operation on that item: 1 click!