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.
This module adds clientside validation (aka "Ajax form validation") for all forms and webforms using jquery.validate. The included jquery.validate.js file is patched because we needed to be able to hide empty messages.
#D8CX: I pledge that Clientside Validation will have a full Drupal 8 release on the day that Drupal 8 is released.
Features Override is used to change (override) existing Features. You may want to use it if:
You are installing a feature module that requires this module.
You have a site built on features - e.g., an Open Atrium or Commerce Kickstart site - and you want to make changes without losing them when you upgrade to a new version.
You are a feature developer looking to selectively override components (Views, content types, etc.) of existing features and export just the changes to code.
Initial 1.x development sponsored by Chocolate Lily. The 7.x-1.x branch was unstable with several reported issues for views (and, likely, panels). That branch has been abandoned with new development occurring in the 7.x-2.x branch (sponsored by Phase2 Technology). Drupal 6 users should continue to use the 6.x-1.x version...no 2.x branch is planned.
NOTE: Overrides exported with version 1.x are NOT COMPATIBLE with overrides exported with version 2.x. If upgrading you should disable the 1.x override, remove the 1.x Features Overrides module, install/enable the Features Overrides 2.x version, then re-export your changes as new overrides.
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.
Video.js is a HTML5-based video player with a built-in Flash fallback for older browsers. This means that videos can be played on nearly all devices and operating systems, provided the right codecs are used.
This module is a support module for Video.js. It doesn't contain Video.js itself, but integrates it with the File, Link and Video modules after you've installed it.
DB maintenance optimizes administrator-selected tables in the database during regular cron.php executions. For MyISAM tables, OPTIMIZE TABLE repairs a table if it has deleted or split rows, sorts table indexes, and updates table statistics. For BDB and InnoDB, OPTIMIZE rebuilds the table. Note, MySQL locks tables during the time OPTIMIZE TABLE is running.
Rather than having to manually copy/paste the Like this on Facebook code for each piece of content you (or your users) create, this module will automatically add that code to the end of each chosen node type. You are able to add a Like button which likes a given URL (static, e.g. your homepage) or/and put a dynamic Like button on your page to like the page you are actually visiting.
OpenLayers supports a wide range of map types and new types can easily be added as ctools exportables - new layer types are being added all the time. Currently the module supports OpenStreetMap, Google Maps, Yahoo Maps, Bing Maps, TMS, WMS, CloudMade, XYZ map types and the MapBox maps.
OpenLayers supports a wide range projections and new ones can easily be added as ctools exportables. Proj4JS is the JS library who allows to create custom projections, so, the proj4js module is now a dependency.
Map interactions like popups, zoom controls, editing, and fullscreen can be added via the UI and extended by other modules.
This module allows for a user interface to create and store maps which can be used to customize all sorts of things like CCK Formatters to Views Plugins. Maps can be provided by code or stored in the database and integrated with Features.
Note: Previously named "Mobile Friendly Navigation Toolbar"
A very simple mobile friendly navigation toolbar introduced as part of the Spark project to solve mobile editing problems with the Drupal 7 shipped toolbar, that is not very friendly to small screen sizes.
This module builds user profiles as content (aka nodes), which opens the opportunity to use all the powerful modules for content for user profiles too, e.g. the Content Construction Kit (CCK). It's intended to be simple and useful, but extensible by further modules.
Content profiles can be restricted to certain roles; the module also supports separate content profiles for different roles.
The Custom Formatters module allows users to easily create custom Field Formatters without the need to write a custom module. Custom Formatters can then be exported as CTools Exportables, Features or Drupal API Field Formatters.
Pluggable editor/renderer engines:
Create simple formatters from existing formatters with preset formatter settings.
HTML + Tokens
A HTML based editor with Token support.
A PHP based editor with support for multiple fields and multiple values.
A Twig based editor provided by the Twig filter module.
Supports for all fieldable entities, including but not limited to:
Drupal core - Comment, Node, Taxonomy term and User entities.
Field collection module - Field-collection item entity.
Media module - Media entity.
Drupal API formatter via:
Custom Formatters export interface.
CTools exportable via:
Custom Formatters export interface.
CTools Bulk Export module.
Live preview using real entities or Devel Generate.
Review your Custom Formatter code for Drupal coding standards and more.
Contextual links(Drupal core)
Adds a hover link for quick editing of Custom Formatters.
Format Display Suite fields.
Adds dependent Custom Formatters (from Views or Content types) to Feature.
Drag'n'Drop interface for builder Formatter Settings forms.
Exposes Custom Formatters to the Insert module.
Adds real-time syntax highlighting.
Adds the Token tree browser to the HTML + Tokens engine.
This module adds a contextual link to the Entity Field panel pane which allows that field to be edited without having to visit the entity's edit page. This field editor will open in an overlay if overlay.module is enabled.
This only affects the entity pane for a single field.
A Trello board is being used to help coordinate development.
Disable breadcrumbs on a per node, per content type, or by path (any path) basis; Omitting the need to write additional code in the theme layer (template.php file etc..) to determine the visibilty of breadcrumbs on specific pages. This can be administered on node edit forms and from the content administration page (node operations) to select/unselect multiple nodes for enabled types.
NOTE: This module has now been rolled into the 3.x branch of Backup and Migrate and is no longer supported independently.
This module is a plugin for Backup and Migrate and does nothing on its own. You must download and install Backup and Migrate 2.x (Aug 24 dev or later) to use this module. This module is not compatible with version 1 of Backup and Migrate.
Defines a field type Block reference which creates a relationship to a block and allows the block to be displayed as the content of the field. It saves this relationship using the block's bid, not its delta + module. Version 2 saves module + delta (moddelta), which is much more robust than bid.
Widget "Select list (with drag-and-drop sort)" has been deprecated. Use Multiple Selects instead!
The Contact form blocks module makes your site-wide contact forms available as Drupal Blocks.
Using this module you can show your contact forms at any place where you can show a Drupal Block. For instance you may add a contact form to the right sidebar of your website which should be shown at every page. Or you want to add another contact form (aka category) to a certain node only. Add the contact form block to the content region and use the Block visibility settings to hide it from all pages but that special one.