Minimally maintained

Provides Custom Breadcrumbs identifiers for node hierarchies based on node reference fields.

This module uses the plupload integration module to integrate plupload into the IMCE file browser.

Plugin to create NewsML Feeds in views

MeSH Auto-Import retrieves all MeSH terms that are associated with a publication's PubMed ID and attaches them to a node's term reference field upon node add/edit.

Deprectated

Since version 6.8.2 GNU GLOBAL comes with its own drupal definition and there are better ways to trigger a reindex on save (i.e. https://github.com/dedi/gxref) this project is not relevant anymore and deprecated.

This project consists of Drush utilities for making the daily life of Emacs users easier.

Currently the project provides two new Drush commands:

• drush etags
• drush gtags

They will run etags/gtags in your DRUPAL_ROOT and generate tag files for use in Emacs and it will help keep them up to date.

This module will hook on to Ãœbercart`s checkout form and provide an AJAX callback for the postal code fields.

Supports Ubercart 3.

Integrates with Bring API and supports the following countries;

• NO - Norway
• DK - Denmark
• SE - Sweden
• FI - Finland
• NL - Netherlands
• DE - Germany
• US - United States
• BE - Belgium

Records all cookies that all users have set when they load a page.

This allows easier auditing of cookies on your websites for conformance with the EU cookie law.

Information appears under admin/reports/cookies

Drupal 8 : As Drupal 8 is now stable for a while, no further development will be done to this module (except security fixes). Popup which is a dependency has no plan for port. Therefore there is no plan to port this module either.

This module implements the integration of the Popup module with Views.

It provides a Views global field that can reuse the other Views fields. It will be output a link that will trigger a popup.

Taxonomy Channels is a D6* module created to allow users quick access to a list of preferred taxonomy terms. Perhaps a better way to think of it is "favourite terms". It is best explained with a use case.

Let's say I have a site about vegetables, and each user wants to pick some vegetable types to "follow". They select these from a list, and the selected ones appear as a list in a configurable block for easy access.

Content Img looks for images in the node body and stores them in the image field