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.
Entity cache puts core entities into Drupal's cache API.
Due to the entity loading changes in Drupal 7, no core patches are required.
How to use it
This module has no user interface, if you enable it, entities will start being cached, if you disable it, they'll stop.
Supported core entities
- Taxonomy terms
- Taxonomy vocabularies
Support for contrib entities:
There is no automated support for contrib entities, to use entitycache for a contrib or custom entity:
- Create a cache_entity_$myentity table/bin.
- Specify EntityCacheDefaultEntityController as your controller class in hook_entity_info(), or extend it.
- Never update your entity tables outside of save/delete API calls.
Entity cache is now set up for automated testing on Drupal.org, see current HEAD status.
Support for the views slideshow: dynamic display block module is given on a daily basis. The issue queue of the module is the preferred place to post: support requests, feature request and bugs. Please give detailed descriptions of your issues, so we can help you better. Searching the issue queue (search on all issue, also the closed ones) can give you direct answers.
Allows users to attach files to comments. Multiple attachments per comment are supported, and comment uploads can be enabled and disabled on a per-nodetype basis.
The development snapshots are intended for testing and development. They are not suitable nor supported for use on websites.
Includes a jQuery PNG Fix to correctly handle PNG transparency in Windows Internet Explorer 5.5 and 6. Make sure to read the documention and be bold! Transparent PNGs on IE result in killed kittens, so this module tries to help that.
Inspired by Geeks and God.
The Custom Formatters module allows users to easily create custom CCK/Field Formatters without the need to write a custom module. Custom Formatters can then be exported as CTools Exportables/Features or Drupal API Formatters.
Changes have been made to the PHP formatters Render Array integration to correctly support multi-field values, this changes the HTML wrappers of the formatter and may affect the theming of your site. This change will be made in 7.x-2.2 and the upcoming development releases.
- Two different editor modes:
- Basic/HTML + Tokens: A HTML based editor with Token support.
- Advanced/PHP: A PHP based editor with support for multiple fields and multiple values.
- Support for:
- Exportable as:
- Drupal API formatter
- CTools exportable/Features
- Live preview ([D6] requires Devel generate module).
- Integrates with:
- [D7] Coder Review module - Review your Custom Formatter code for Drupal coding standards and more
- [D7] Drupal Contextual links module - Adds a hover link for quick editing of Custom Formatters.
- Features module - Adds dependent Custom Formatters (from Views or Content types) to Feature.
- [D7] Form Builder - Drag'n'Drop interface for builder Formatter Settings forms.
- Insert module - Exposes Custom Formatters to the Insert module.
When a user edits their account details they can choose to upload an image or photo of themselves, also known as an avatar. The Avatar Selection module allows the user to pick an avatar image from a list already loaded by an administrative user. It is also possible to disable the uploading of pictures by users and only allow them to select an avatar icon from this list.
No images are supplied with this module. It is recommended that all images you use are roughly of the same size.
All of the current work on Avatar Selection is done by one developer. It is likely that I will not be able to add all requested features, unless there is some community funding for this project. So if you want to show your appreciation for the Avatar Selection module development or would like to see new features added, please consider donating to this project.
This module allows the site admin to create custom error pages for 404 (not found), and 403 (access denied), without the need to create nodes for each of them.
Spaces is an API module intended to make configuration options generally avaliable only at the sitewide level to be configurable and overridden by individual "spaces" on a Drupal site. It has been described as:
- A way to make one Drupal site act like several sites
- A way to provide much more configurable, full-feature Organic Groups or user homepages
- A generalized API for contextual configuration
Requirements & compatibility
Use of spaces requires
However, you will want the following modules in order to build or use reasonably cool features with Spaces and take advantage of most space types:
Out of the box, Spaces provides integration modules for:
This module enables users to subscribe to be notified of changes to nodes or taxonomies, such as new comments in specific forums, or additions to some category of blog. Once enabled, all nodes will have an additional link that allows the user to change their subscriptions. Users have tab on their user screen to manage their own subscriptions. Users can also set an auto-subscribe function which notifies the user if anyone comments on posts they have made. Admins can turn this on by default.
Subscriptions has its roots in 2003 (node/4189!). At version 5.x-1.x it was in a crisis, due to too many people having pulled in too many directions. In Winter '07 and Spring '08 it was rewritten from the ground up by chx and salvis, and we are maintaining it to this day.
The Beautytips module provides ballon-help style tooltips for any page element by integrating the BeautyTips jQuery Tooltip plugin by Jeff Robbins with Drupal. It provides an API for adding custom beautytips as well as some built-in features. Admins can enable rollover balloon-help style tooltips for text fields within forms. It also supplies hover tips for Drupal help links and advanced help links.
Most importantly, it allows developers to add their own custom beautytips popups to their site without having to delve into jQuery.
Check out this cool informational video for info on how to use BeautyTips to enhance your Drupal views. Note: This video is using version 6.x-1.x and there have been some changes since then, so consult the documentation before using.
This module provides a way to specify a certain level of password complexity (aka. "password hardening") for user passwords on a system by defining a password policy.
The advanced user module allows the filtering of users based on the user.module fields and optionally the profile.module fields. The fields available for filtering can be configured using the module settings. Eg. Site admin may search through 1000s of users to display all users who have not accessed their account.
Once the group of users with selected common denominators are filtered, the module can be used to perform functions that email, block, unblock, add or remove roles, or delete. Another nice feature is the ability to notify administrators or other roles, by email, of user account creation or profile changes.
I am looking for a co-maintainer of this module. Please let me know of you interest using the contact form.
NOTE: Version 6.x-3.x or 7.x-3.x is the release to use. The Drupal 6.x-2.x-dev release is no longer being updated.
Pay close attention
I have begun the modifications for feature enhancements. The module directory and file structure is being changed. If you upgrade to this version of the module you will need to completely remove the previous version of the module (cd sites/all/modules && rm -rf advuser) before installing this version.
The -dev version is functional
I have converted the Advanced User to Drupal 7 using the 3.x series. You should be able to use this module in your Drupal 7 environments. I will be creating a release candidate by June 30th, 2012 or before.
- Adding tags to media when uploading
- Pulling down title and description information from web based media sources
The module is still in development and more features should be coming soon. Based on the feature requests in the issue queue and my own thoughts I would organize the features for Media Browser Plus into two categories. Functional and organizational.
- Click and drag to select multiple files
- Selecting multiple files with shift or ctrl
- Searching media
- Contextual links and actions
- Hierarchical taxonomy based organization e.g. “folders”
- Uploading or importing a file structure into a taxonomy hierarchy e.g. the directory tree in a zipped upload gets converted into the “folders” taxonomy
- Updating and applying taxonomies read from media files e.g. tags added to images
- Personal and public “folders”
- Shared “folders” either by user or role
This module allows you to embed a view as a field in a view. A new field handler is made available, so this can also be used in area (header/footer/empty) handlers as well as rows.
This view handler can accept arguments from fields of the parent view using tokens and pass them into the child view for each row. Raw or rendered token values can be used, as well as static values.
Workbench Moderation adds arbitrary moderation states to Drupal core's "unpublished" and "published" node states, and affects the behavior of node revisions when nodes are published. Moderation states are tracked per-revision; rather than moderating nodes, Workbench Moderation moderates revisions.
In an effort to minimize the duplication of jcarousel based modules this module is being deprecated for the Drupal 6 version onward and is being replaced by the jcarousel module. As of the Drupal 6 2.x branch of the jcarousel module views integration is provided.
The carousel module, jcarousel module, and this module are being merged into one effort with the maintainers combining efforts in one module.
Drupal 5 Version
The Drupal 5 version of this module is maintained by recidive
Current status: This module is in development. Use it with care on any production sites.
Drupal 6 Version
Use the jCarousel module version 2.x.
Drupal 7 Version
Move to the jCarousel module.
This module enriches Views2 functionality with SQL Grouping and Aggregation capabilities.
Ever wanted to design a view that displays top terms for a specific node type and number of nodes for each top term? You could not build such query before, but now you can.
A new field group: SQL Aggregation is added, in Views, once you install the module. The field group has one available field: SQL Aggregation: Group By Fields. The field allows to configure many aspects of "group by" SQL clause and "count()" fields.
Currently only SQL COUNT() function is available due to a limitation in Views2 API. We are working on a Views2 patch to overcome the limitation. Patch will be submitted to Views2 project and, hopefully, applied shortly thereafter.
You can read a Quick-start Tutorial to get up and running with the module in no time.
Please make sure that when you add/order fields, Views GroupBy field is the last field in the list!
Custom Pagers allows administrators to define context-sensitive previous/next pagers for any node type. The list of nodes to be cycled through is generated by a user-selectable view, and each pager can be displayed above or below the node body or in a sidebar block. This makes it possible to duplicate the paging functions of forum.module and book.module, as well as more complex stuff like comic strip navigation. Requires token.module and views.module.
If you only need a simple previous/next pager for a specific content type, check out Flippy.
Feeds Tamper provides a small plugin architecture for Feeds to modify data before it gets saved. Several plugins are available by default and are described in the examples section below. Additional plugins can be added in separate modules or through the issue queue.
Redirect the HTTP 403 error page to the Drupal /user/login page with an optional message that reads:
"Access denied! You must login to view this page."
Also, the desired page is appended in the url query string so that, once login is successful, the user is taken directly where they were originally trying to go.
Token Filter is a very simple module to make token values available as an input filter.
The module now supports native tokens (e.g.
[site:name]) and all global tokens by default. It even allows some contextual tokens like node or user to be replaced, but currently does not encourage users to use them in the filter help text.
Drupal 6 and 5
- In the text where you use that input filter you can use substitution tokens with
[token global site-name]etc. You can use the global context, the user context and any custom context available. You need to enable the Token Filter for any of your existing filter types first.
- At present, the node context is not available. See #474424: Code doesn't verify the value entered by the user, and calls token_replace() with the wrong arguments
The Drupal 5 version only replaces tokens of type global and user.
Note: FeedAPI versions lower than 1.9 are not compatible with Drupal 6.14 or higher (see #580508 for details).
FeedAPI aggregates feeds on a Drupal website by generating light weight items or nodes from feeds. It provides a straightforward configuration for most use cases and is extensible through an API. FeedAPI integrates with OG (but does not require it).
Note: Zenophile is not compatible with the new 7.x-5.x (HTML5) branch of Zen, and probably never will be, particularly since Zenophile itself supports automatic subtheme generation via Drush now. Thanks for a good run, loyal Zenophile users!
Zenophile allows themers to very easily start new Zen subthemes without all the tedious file copying and find-and-replacing required when creating subthemes by hand. It also simplifies other common tasks when creating Zen subthemes, such as adjusting the width and placement of some page regions. Zenophile includes a simple API allowing developers to create their own modules to modify Zenophile's behavior and add their own features.
Date iCal is your one-stop shop for iCal support in Drupal. It provides a plugin for Views to enable outputting your site's calendar as an iCal feed, and a plugin for Feeds to enable import of external iCal feeds into your site's calendar.
Any entity which contains a Date field can be utilized by Date iCal for import and export of iCal feeds.
Date iCal 2.0 is a complete re-write of most of the project's internals. Rather than using Drupal's theme system to build the iCal output, we now use the iCalcreator library, by kigkonsult.
In addition, Date iCal 2.0 introduces the ability to import iCal feeds from other sites, through use of a Feeds plugin.
The dependencies for Date iCal 2.0 are as follows: