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.
First there were modules, then there were Features, and now there are Apps. Apps is the next generation of extensibility and interoperability for Drupal. They provide a much better user experience of extending your Drupal site by providing facilities to download modules and all of their dependencies in one easy step.
You can hear more about Apps at the following Drupalcon Presentations
UUID Features 7.x-1.0-alpha3 fixes some HTML code that made the module completely unusable. Please update ASAP. If you're experiencing WSOD simply remove the module files completely then upload the latest version. The latest version now works with UUID 7.x-1.0-alpha3. Please report any bug you encounter in the issue queue.
The UUID Features Integration module provides a mechanism for exporting content (nodes, taxonomy, fields) into a features module. What's that you say? You thought features was only for configuration? This module is meant to be used in the cases where certain pieces of content straddle the line between pure content and configuration.
There are relatively static pages (like an About Us page) that have links from your primary navigation. If these were to go missing, your client would certainly say the site is broken.
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.
Once the Apps module is enabled, go to admin > apps. You should see a list of available apps. Click details for SEO Essentials and then "install app". All required modules will automatically download and enable. Follow the instructions in the setup wizard to complete configuration.
As a stand alone module
Download the SEO module from the link below and place the files in your site’s module directory. Go to admin > modules and review any missing dependent modules for SEO Essentials. Download those modules from Drupal.org. Enable the SEO Essentials module when all dependent modules are available.
Important: This module is deprecated. See Commerce Backoffice for a more advanced set of Commerce backend views and related functionality.
This is a feature containing replacement VBO views for the main Drupal Commerce admin screens, including Products, Orders, and Content. This allows you to mass-delete content, orders, and products, etc.
This module pulls together the techniques Jeff Eaton outlined in http://www.lullabot.com/articles/photo-galleries-views-attach to automatically create a simple gallery where each gallery is a node with an embedded view of images that were assigned to that gallery. The module creates the content types, sets up the imagecache presets, creates the default gallery view that is embedded into the gallery nodes by Views Attach, and adds css to make it all look nice.
This technique also works well to create individual image galleries for Organic Groups, since the gallery and image content types can be configured as group nodes. Views Gallery OG, included in this package, provides a setup page to make it easy to automatically create a gallery for every group and adds group context to the forms wherever possible so the right groups and group galleries are pre-selected when you create gallery images.
This module is mostly a bit of glue around numerous other Drupal modules. It is a perfect example of something the Features module was designed to do, and it is being reworked as a Feature instead of using custom .install code. All new development will be on the Features version. The versions are:
The 6.1 branch is the original code, which does not use the Features module.
The 6.2 branch is the new code, which requires Features, Strongarm, and CTools.
See the README.txt for instructions about how to upgrade from 6.1 to 6.2.
This module is intended to be a lightweight gallery solution with a simple feature set that you can tweak using the CCK and Views UI and some custom css in your theme. If you want a robust gallery with advanced features, this is probably not the right module to use. If you need a quick and simple gallery solution built on modules you are likely to use elsewhere, this may be a good fit.
Provides various content administration enhancements and other elements required for Open Enterprise content apps. It's purpose is to bring handy Open Enterprise UI improvements into any Drupal 7 site and to enable Open Enterprise content apps to be used on any Drupal 7 site.
The main feature of this module is to provided some simple yet effective improvements to content admin workflows. The module adds a default admin view that is filtered by content types. This view can be overridden to show content type specific data, e.g. the date of an event. The module also adds two contextual links "+ Add [content type]" and "+ Administer [content type]" to any standard view that is filtered by content type.
There are a few ways you can quickly add this to a site:
Traditional manual install by downloading the Enterprise Base module and dependencies from Drupal.org
Features tools is a development helper module for working with the fantastic Features module.
The main goal of this tool is to give the ability to remove elements from a feature and put them back to the DB.
It adds a "Safe Create Feature" button to the recreate feature form, which detects the element that has been removed from the feature and saves them in an unlink file.
In order to save the elements to the DB you need to go to the admin/build/features/unlink page, check the element you need to import and submit. Please watch this screencast.
Right now we support the unlink of views ,rules and boxes modules.
If there is a real need to unlink other elements please open an issue.
Features direct save
Adds a submit button in the recreate feature form, named "auto create feature" which downloads the feature tarball, un-tars it and put the files in the right place. All in one click!
Anyone who uses the recreate feature more than few times a day,
will probably like this module :)
In order to make the module to work you need to give the web server permissions to write to sites/all/modules directory. THIS TOOL MODULE IS FOR LOCAL SERVER DEVELOPING ONLY !!!
Updating existing vocabularies and terms, with the following caveats:
Updated items must have the same VIDs / TIDs. Just because two things are named the same doesn't make them the same. It is safest to attempt updates only on the same site the export was originally taken from.
When updating you must explicitly state (with the dropdown selector) which vocabulary you want to update.
Currently, updating vocabularies using the IPAPI function install_taxonomy_export_import_from_file() is not supported.
Because of limitations in Drupal's taxonomy.module implementation certain things will, likley, never be possible. For example, detecting malformed imports that could cause collisions.
Profiler Builder is a module for automating the creation of installation profiles and distributions. It has support for the Profiler installation profile simplifier library but is able to run independent of it (1.0-RC4+). This module creates a downloadable tar package that gives you a well made installation profile and associated drush make file based on the site its installed on.
This is a fast, simple way of creating a distributions from any produced drupal site and is an excellent form of documentation via blue-print creation.
Builds the .info, .profile, .install, .make, and .make.example files necessary to turn a site into a distribution / installation profile and tar's them up as a download.
Checkbox settings to allow for modifications to the generated output
all files based on components selected and analyzing current site
.install setting based on common install routines and distribution best practices
Make files features:
Local development options and components not found on d.o. added to local.make.example
modules with version and custom / version-less modules added to the end
A Work tracker for Open Atrium 2.0 (similar to the Case tracker in Open Atrium 1.0) which allows you to create Tasks in order to collaborate on work.
Work Tracker is designed to fit seamlessly into the way Open Atrium 2.0 works and it’s paradigm for flexibility. For example, Work Tracker has no concept of “projects” - instead it groups Tasks together using Open Atrium Sections, which allows users to define for themselves what a “project” is in a way that best fits their organization.
Suggestions, bug reports and patches are welcome in the issue queue!
Install OpenAtrium 2.0 (version 2.0-rc1 and later install Work Tracker by default!)
Create a new Space
Create a new Section inside that space, and select "Tasks Section" under "Section Type" (it's below the body and "Weight" fields).
Using the add button in the header (looks like a '+' sign), create a new Task!
Setup and display to user toolbar style navigation menu (on top of page by default). A toolbar is set of shortcuts (link items) configured by the site administrator (or users with "administer toolbar" permission).
This module is not a backport of the D7 Toolbar Module, it takes the original idea and implements the shortcut feature. This module has been inspired and takes some ideas from Admin and Admin menu modules.
Create and manage toolbars and shortcuts,
Set toolbar per role,
Set toolbar per user,
Show help for the page where the shortcut points (based on path),
Users can select toolbar ("select toolbar" permission),
This simple Feature for Drupal Commerce provides an On sale checkbox and Sale price textfield that can be used on a per-product basis to override the normal price of the product. It comes with a rule for applying the discount which is enabled by default.
Enterprise Rotator is a complete rotating banner solution. It is build as a feature with a content type for each banner item and all the pieces needed to make the rotating banner work. It should not be confused with modules like views_slideshow or viewscarousel.
Check out OpenEnterprise for a great distribution to install Enterprise Rotator.
It is a feature module. This means that it was built using exported features configuration and can be easily modified with the Features Override module.
It is a app module. This means it can be installed using the very awesome and easy to use apps system.
It contains a content type and view for entering and displaying banner items.
It contains Image Styles for automatically scaling each of the images..
Part of the Debut features set, Debut Wysiwyg provides Wysiwyg module integration including configuration for Wysiwyg editing and accompanying input formats and Media module integration for adding file assets to text areas.
Like all Debut features, Debut Wysiwyg can be integrated either as a stand-alone feature to quickly add Wysiwyg functionality to any Drupal site or as part of a Drupal distribution. Debut Wysiwyg is used in the Open Outreach Drupal distribution aimed at nonprofits.
You have three options for installing Debut Wysiwyg:
Install Apps and the Debut Apps connector module and install Debut Wysiwyg as an app. The apps system utilized by Debut Apps uses the same installation mechanism as the Update module in core. Apps will download all the required modules, making it an easy way to install Debut Wysiwyg.
Debut Wysiwyg is used in the Open Outreach Drupal distribution aimed at nonprofits, so you can install it as part of Open Outreach.
Install manually along with the dependencies listed below.
Three input formats: Wysiwyg public, Wysiwyg contributor, and Wysiwyg editor.
A Wysiwyg profile for each of the input formats, including edit buttons designed to meet the common editing needs of users with varying roles.
Incorporates the Media module for inline insertion of media.
Uses the Entity module to export the input formats.
A Drush Make.make file with all dependencies, including the CKEditor.
Part of the Debut features set, Debut Event provides an event content type, calendar displays, and associated views, contexts, and Media module integration.
Like all Debut features, Debut Event can be integrated either as a stand-alone feature to quickly add event functionality to any Drupal site or as part of a Drupal distribution. Debut Event is used in the Open Outreach Drupal distribution aimed at nonprofits.
You have three options for installing Debut Event:
Install Apps and the Debut Apps connector module and install Debut Event as an app. The apps system utilized by Debut Apps uses the same installation mechanism as the Update module in core. Apps will download all the required modules, making it an easy way to install Debut Event.
Debut Event is used in the Open Outreach Drupal distribution aimed at nonprofits, so you can install it as part of Open Outreach.
Install manually along with the dependencies listed below.
Event content type with date field.
Calendar view with upcoming events block and RSS feed.
Panopoly News is both a simple news content application and a great starting point for building more robust and powerful news applications. It installs pre-configured with sane defaults so you can immediately focus on adding content instead of spending time with difficult setup. However, you can also easily customize and extend Panopoly News to fit your needs. Beyond all the great features inherited from Panopoly, Panopoly News offers the following:
Simple Design - Sleek, smooth and easily customized design... and with panelizer you can change the layout and position of your content.
Good Default Functionality - Free tagging, Related Content, Featured Content, More by this Author and RSS... and with the In Place Editor you can customize every display.
Easy Configuration - Easily add content, configure your app and remove or add demo content with the improved toolbar... and integration with the Apps module means it is easy to add in your own configuration and default content.
Admin Experience - Easily edit and/or delete your content with contextual links. No more clicking 5 links to find what you are looking for.