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.
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.
This module has not been ported to Drupal 8. Refer to this issue to find out its progress.
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.
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
Drupal 8 Version
For best results use Drush to export nodes to a specific module. Any node is supported along with its menu links. Path alias is not working yet because of a core bug. Whenever a module with exported content is enabled, its content will be imported. Each node has an export tab which presents the user with a file downoad but only of the node, not of the menu item. In addition a page has been started which lists all the exported content visible to the site. More work is needed on the UI and on language support.
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
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.
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.
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.
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 !!!
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!
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
Note: If you are looking for Lightning Features in 8.x; see the 8.x-1.x branch of Lightning here.
This project contains the decoupled components that are maintained for the Lightning distribution project. You can add this project to your own install profile and build unique sites that leverage the power of Lightning.