Modules

Checkbox Validate

Corrects bugs in Drupal core:

• Checkboxes set as required not displaying required symbol (install this module to display)
• Checkboxes set as required behave as optional (install this module to make behave as required field)

Note: developers don't need to add any extra validation code to their modules to make up for the bug in core, and once core is fixed this module can be uninstalled: #856452: Please test the core patch to help fix this bug in Drupal core - Mark this module as obsolete when that happens

This is the related D6 issue: #259292: Required radios/checkboxes are not validated (D6). More experienced users should head there and help fix this in core by testing the latest patch.

This core bug has been fixed in D7: #179932: Required radios/checkboxes are not validated

Developed by Robert Castelo for Code Positive

Automated Logout

This module provides a site administrator the ability to log users out after a specified time of inactivity.

It is highly customizable and includes "site policies" by role to enforce logout.

Discussion Thread:
#925818: should the one session feature be removed from autologout?

Includes content submission detection after timeout to prevent users loosing work.

7.x-4.x-dev Branch

This is a huge re-vamp of the x.x-4.x branches. It was based of the 6.x-4.0 branch. It has been upgraded to work with drupal 7 and adds several new features. Such as having different timeouts based on roles. You can now also set timeouts based on individual users. So user 4 can have a different timeout then user 5 even if they are in the same role! There is also the option to set a permission so that users in selected roles can change their own timeout value. With a configurable maximum timeout! Currently this is in dev however after some further testing it will be moved to beta. Feel free to try this new version out and post any bugs or other issues to the issue queue!

Optional integration with:
Javascript Timer (Autologout 6.x-2.5 and after).
Javascript Countdown Timer (Autologout 6.x-2.4 and previous).

6.x-4.x Branch

Javascript Tools

Javascript Tools provides a common set of methods extending those available in Drupal core (drupal.js) for Javascript and AJAX module development in Drupal.

Note: you should not install this module for Drupal 6 unless it is required by another module.

Note: As of Oct. 20, 2009, the 5.x version is no longer supported.

Prior to Drupal 6, Javascript Tools included an integrated set of Javascript and AJAX modules. For Drupal 6, modules previously part of Javascript Tools now have the following separate projects:

Active menus, http://drupal.org/project/activemenu (requires Javascript Tools 6)
Collapsiblock, http://drupal.org/project/collapsiblock (requires Javascript Tools 6)
Tabs: http://drupal.org/project/tabs
Active edit, http://drupal.org/project/activeedit (prototype only as yet, not usable)
Ajax submit, http://drupal.org/project/ajaxsubmit

Install Javascript Tools 6 only if you use Active menus or Collapsiblock or another module that requires it.

Translation Overview

The Translation Overview page provides a table listing the site's nodes and showing what's been translated into each language. It also lets you assign priorities for translating nodes into the various languages.

For translations of taxonomy terms and menu items check out the Translation table module.

Contributors

The Drupal 6 version of this module was designed by sticky and maintained by drewish.
The Drupal 7 version was initiated and sponsored by MD Systems (Developer: Miro Dietiker).

Invisimail

Invisimail provides a content filter to hide email addresses from spam-bots. Email addresses are converted to ascii code and optionally written to the page using a concatenated JavaScript "write" command. The email addresses will appear on the page normally, but their html source will be obscured so as not to appear as an email address to email harvesting robots. Invisimail also provides an option to automatically create mailto links for email addresses.

Obviously, the best protection is not to publish email addresses at all. But on a community site, some users are going to do this regardless. Invisimail provides protection for these email addresses.

Note that you may need to set the invisimail filter to apply after any modules that modify HTML, such as HTML Filter, depending on the settings you select for each.

Notes on versions

- The Drupal 6 version is in maintenance mode. There will be no more work on it aside from critical bug fixes. This module requires PHP 5.2.

- The Drupal 7 version is a heavy rewrite and is now an extensible framework. API information is provided in the module to add additional encoding mechanisms.

Originally written by Jeff Robbins with Lullabot.

Form Builder

This project allows users to build entire Form API structures through a graphical, AJAX-like interface. It has the ability to read and export FAPI arrays, and users are permitted to change any properties exposed by modules that expose forms to the Form Builder.

User Points

This module provides an API for users to gain or lose points for performing certain actions on your site.

In conjunction with other modules, such as the Userpoints Nodes and Comments users can accumulate points for actions such as posting nodes, commenting or moderation duties.

Use one of the many contributed modules to extend the functionality of the module to include point accumulation on page views or votes, upgrade roles based on point balance, or purchase goods from your store.

This module is useful in providing an incentive for users to participate in the site, and be more active.

Userpoints is included in the Drupal Commons distribution.

Block Theme

#D7CX: I pledge that BlockTheme will have a full Drupal 7 release on the day that Drupal 7 is released.

BlockTheme allows an admin to define tpl files for standard block templates and provides a select box on the block configure form so the user can select a tpl file to use as opposed to having to override the templates by block ID.

See an excellent video by Bob @ mustardseed on how to use this module (6.x version)

Fusion Accelerator

Paired with the powerful Fusion base theme, Fusion Accelerator puts easy point-and-click styling of basic Drupal elements within easy reach of site administrators. The philosophy behind the Fusion theming system hinges on applying Drupal’s inherit modularity to the theme layer. This system brings the ability to easily tweak the styling of a site, create new content or re-arrange a site’s layout to site administrators or builders who do not have traditional theming skills.

Google +1 Plus One and Badge

Add the Google +1 Plus One to your nodes, or as a block. No need to copy/paste anything, it works out-of-the-box.

Also you can add the new Google+ badge as a block.

Remember to enable permission for anonymous users.

News

[27/01/2012] Google: New settings soon for Google Badges (Added in 7.x dev branch. I will add the extra settings ASAP to the 6.x branch).
[17/11/2011] Article: The dilemma: Aliased or non-alised URLs in the Google Plus One Button?
[16/11/2011] Google releases Badges, so users can follow your Google+ page without leaving your website. It's ready in the 7.x and 6.x dev releases.

There is a new forum for Google+ developers

Troubleshooting

I don't see the Google Plus One button

• Be sure to enable the permission to view the button for anonymous.

Webform Block

Allows embedding a webform node into a block which can be positioned in any block region (theme space permitting).

Rate

#D8CX: I pledge that Rate will have a full Drupal 8 release on the day that Drupal 8 is released.

"The cck model for voting with Drupal" (source)

This module provides flexible voting widgets for nodes and comments.

Administrators can add multiple widgets. By default, there are 8 widget types to choose from:

• Thumbs up
• Thumbs up / down
• Number up / down
• Fivestar
• Emotion (this makes me mad, angry...)
• Yes / no
• Slider
• Custom

By using "custom" you can customize the rating buttons and Voting API mode. Widget types can be extended by other modules. Other features include:

• Views integration
• Nodes get an extra tab with voting results per widget, which shows:
  • Total vote count
  • Average rating
  • Total points (for thumbs up / down)
  • Vote count per button
  • Chart of vote count per button, per day
• Multiple ratings on the same node (i.e. for "comfort", "location", "services" etc.)
• Voting can be closed at a configurable period after node creation
• Start- and enddates can be configured per node, per widget

Widgets

Widgets enables you to centrally manage and configure code snippets on your site such as share and follow buttons or Twitter updates and Facebook like boxes. It implements a user interface that allows you to easily organize and configure various widget elements. Using a UI similar to core’s image styles, elements can be assembled into widget sets which can be reused throughout the site via blocks and other render displays.

The Widgets module is primarily a user interface API and as such includes only generic markup widgets. You can add new custom widgets using the widget definition admin or enable modules that provide widgets. There are several dozen widgets available through the Social media and Service links modules.

Usage

1. Installation. Use standard methods to install the Widgets archive files into your Drupal site. Then go to admin > modules and enable the Widgets module. You will want to install the Social media and/or Service links modules also to provide widget sources.
2. To display widget sets on your site use the blocks admin at admin > structure > blocks or other method for managing blocks such as Context or Panels. Look for blocks that start with the label "Widgets:" Several pre-built widget sets are provided by the Social media module.

CAPTCHA Pack

The CAPTCHA Pack module contains several CAPTCHA types for use with the CAPTCHA module. The CAPTCHA Pack module is meant to provide lightweight, yet effective alternatives for the traditional image CAPTCHA, which is undesirable in certain situation (e.g. bandwidth restrictions, cpu restrictions, accessibility constraints, etc).

Content Optimizer

The Content Optimizer module helps to increase your site’s search engine (e.g. Google) rankings by improving on-page optimization factors and insuring your content conforms to Drupal SEO best practices. It enables a quick SEO analyzer that provides instant analysis of any site content as a quick and easy guide to assure SEO best practices are consistently followed. The analysis displays vital content statistics and recommendations for improving search engine rankings.

Watch the Content Optimizer screencast demo

Leveraging the Content Analysis API it provides multiple interfaces to quickly analyze any page on your Drupal site (or any page on any website for that mater):

• Node edit– enables you to optimize content while adding or editing nodes without having to leave the node edit form or saving the node. (node edit demo)
• Block – Provides a block to search optimize any page on your site including themed nodes, views, panels and coded pages. (block demo)

elFinder file manager

elFinder is a open source AJAX file manager

Features:

• Integrated with WYSIWYG API capable editors: CKEditor, FCKeditor, TinyMCE, BUEditor (D6), jWYSIWYG (D6), YUI, WYMeditor
• Multiple file upload
• File copying/moving with Drag & Drop support
• Quick file and directory rename
• Image resizing
• Lightbox-preview
• Contect menu with generic file/directory operations
• Inline text file editing
• Favories directory list
• Directory selection history
• Working with archives
• File descriptions

Upcoming 2.x version additional features:

• Drag and Drop file upload
• Drupal file table integration (including Private filesystem support)
• Search
• Visual image resize, crop and rotation
• Role based access control

Module/Library version compatibility list

Varnish HTTP Accelerator Integration

This module provides integration between your Drupal site and the Varnish HTTP Accelerator, an advanced and very fast reverse-proxy system. Basically, Varnish handles serving static files and anonymous page-views for your site much faster and at higher volumes than Apache, in the neighborhood of 3000 requests per second.

This module provides admin-socket integration which allows Drupal to dynamically invalidate cache entries, and also lets you query the Varnish admin interface for status, etc.

Compatibility

At the moment, using Varnish to any effect at all requires Drupal 7 or PressFlow.

We currently support Varnish 2.0, 2.1 and 3.

User Import

Import users into Drupal or update existing users with data from a CSV file (comma separated file).

Revisioning

Revisioning is a module for the configuration of workflows to create, moderate and publish content revisions.
You use it in scenario's like this:

• Authors write content that prior to being made publicly visible must be reviewed (and possibly edited) by moderators. Once the moderators have published the content, authors should be prevented from modifying it while “live”, but they should be able to submit new revisions to their moderators.
• We shouldn't have to grant these roles “god-like” powers (e.g. D6's "administer nodes" permission) to implement this.

Advertisement

The ad module is a powerful advertising system for Drupal-powered websites. It supports the random display and tracking of graphical (banner) and text ads. Ads can easily be displayed in themes, blocks, or embedded in site content. The module records comprehensive statistics about when and how often ads are viewed and clicked, including a plug-in module for generating graphical time-based reports. Ads can be assigned to multiple owners, each of which can be assigned their own set of permissions. Installation is simple by design. An API is provided allowing the development of additional functionality and integration with other Drupal modules.

Taxonomy Breadcrumb

The taxonomy_breadcrumb module generates taxonomy based breadcrumbs on node pages and taxonomy/term pages. This module fixes the common complaint of having "Home" be the only breadcrumb on node pages. The breadcrumb trail takes on the form:

[HOME] >> [VOCABULARY] >> TERM >> [TERM] ...

Simply install the module and taxonomy based breadcrumbs will appear on node pages and taxonomy/term pages. For the most common applications this module will work "out of the box" and no further configuration is necessary. If customization is desired settings can be changed on an administration page.

Publish Content

This module

• enables granular publish and unpublish permissions:
  • global (un/publish any content)
  • per "node type" (un/publish any [nodetype] content)
  • per user (un/publish own [nodetype] content
• adds a "Publish/Unpublish" tab to the node page for one-click un/publishing.
• exposes publish/unpublish links to your views, making it easy to streamline workflows for reviewers, editors and publishers.
• is lightweight and always will be.

After enabling it, you just need to go to the Drupal permissions page, and set the various permissions:

• "publish any content": you can publish any node
• "publish any 'nodetype' content": you can publish any node whose type is 'nodetype'
• "publish own 'nodetype' content": you can publish any node whose type is 'nodetype' authored by you
• "unpublish any content": you can unpublish any node
• "unpublish any 'nodetype' content": you can unpublish any node whose type is 'nodetype'
• "unpublish own 'nodetype' content": you can unpublish any nodes whose type is 'nodetype' authored by you

It's almost too obvious to write: click the 'Publish' tab to publish and 'Unpublish' to unpublish. It's that simple.

Entity Translation

The beta2 release features a huge amount of changes with respect to alpha2, please read carefully the release notes before installing it.

Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation for the new translatable fields capability in Drupal 7. Maintained by the Drupal core i18n team.

This project does not replace the Internationalization project, which focuses on enabling a full multilingual workflow for site admins/builders. Some features, e.g. content language negotiation or taxonomy translation, might overlap but most of them are unrelated.

Integration

• Title module allows to replace entity labels with fields to make them translatable.

Dependencies

Entity Translation requires core version at least 7.15.

Usage

• Drupal multilingual guide
• Blog post: How to setup entity translation by Randy Fay rfay
• General overview of features (with screenshots) in a Drupal core issue

Mobile Tools

Description

The Mobile Tools module provides Drupal developers with some tools to assist in making adjustments to your site based on the visitor's device.

• Contextual switching of content and layout
• Exportable configurations using Spaces and Features
• Define your sites via domain, sub domain, path, path pairs and query string
• Server side feature detection using Browscap
• Automatic redirection to a site based on device group
• Mobile bookmark popup/Add to home screen notification
• Media Query builder
• anything else we can think of!

Mobile Tools integrates with the following modules to enable the described functionality

• PURL
• CTools
• Context
• ThemeKey
• Browscap
• Spaces
• Panels
• Features
• Context HTTP Headers

Mobile Tools 3.x

Updates:

• #1717242: Add support for browser parent detection in mobile_tools_browscap
• #1713558: Add support for "Chosen" to select user agents in mobile_tools_browscap
• #1687834: Remove strict dependency on Spaces

editablefields

This module allows CCK fields to be edited on a node's display (e.g. at node/123), not just on the node edit pages (e.g. node/123/edit). It also works within views etc. Anywhere a 'formatter' can be selected, you can select editable (or click to edit).

This module has been totally re-written for Drupal 6, and it is very much simpler.

Unless you want to help testing/developing the 3.x branch of this module, please use 6.2 version of this module.

Drupal 6

For Drupal 6, you may now use the normal mechanisms in both content type fields and view fields to select that a field should be 'editable'. If you have the correct permissions, the corresponding field will be displayed in it's editable state. This is done using ajax (and javascript), which means if the users browser has not got that enabled, then fields will not show as editable - sorry.

When a field is not shown as editable (because of permissions, or no javascript) then the default display is used.

Short how-to:

• Create yourself a content type.
• Add a field.
• In the content type's "display fields" tab, edit the display of the field for e.g. 'full node' to be editable.
• Create a new node of this content type and save it.
• Now go and visit this node. You will find that you can edit the field.
• Likewise you can select editable as a display type in a view.