Search form

Download & Extend

497 Modules match your search

Maintenance status

Development status

Module categories

Core compatibility

Status

Search Modules

Sort by

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 is designed to provide a way to export large amounts of data from views. It provides a display plugin that can rendered progressively in a batch. Style plugins are included that support exporting in the following types:

CSV

Microsoft XLS

Microsoft DOC

Basic TXT

XML.

Advanced usage

This module also exposes a drush command that can execute the view and save its results to a file.

drush views-data-export [view-name] [display-id] [output-file]

Requirements

The batched export functionality of this module requires a MySQL database.
This module also requires version 2.7 or higher of views.

Similar modules

Views Bonus Pack includes an export submodule that allows exports, but is not scalable for large data sets.

Views Datasource allows exporting to XML/JSON among many others, but is geared towards small exports.

The migrate module provides a flexible framework for migrating content into Drupal from other sources (e.g., when converting a web site from another CMS to Drupal). Out-of-the-box, support for creating core Drupal objects such as nodes, users, files, terms, and comments are included - it can easily be extended for migrating other kinds of content. Content is imported and rolled back using a bundled web interface (Migrate UI module) or included Drush commands (strongly recommended).

This module allows users to export nodes and then import it into another Drupal installation, or on the same site.

Using this module you can save yourself a lot of time setting up new websites that have similar nodes to websites you've already made, migrating nodes to new Drupal versions, or between development/staging/production sites.

You will need the same content types for the imports to work (unless using Feeds to import), and ideally relevant compatibility with fields, and modules.

Migrate Extras extends Migrate to provide support for several contributed modules.

The best place to implement migration support for a contributed module is in that module, not in the Migrate or Migrate Extras modules. That way, the migration support is always self-consistent with the current module implementation - it's not practical for the migrate modules to keep up with changes to all other contrib modules. We are no longer adding support for other modules to Migrate Extras.

Status

Migrate Extras 2.5 is now available. This is planned to be the final Migrate Extras release - the only work to be done with Migrate Extras going forward will be to port the contrib module support here directly to the respective supported modules.

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.

Overview

The Lightweight Directory Access Protocol (LDAP) project provides integration with LDAP for authentication, user provisioning, authorization, feeds, and views. It also provides apis and building blocks (query and server configuration storage) for other modules.

Date iCal is your one-stop shop for iCal support in Drupal. It provides a plugin for Views to enable exporting your site's calendar as an iCal feed, and a plugin for Feeds to enable importing 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.

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.

This module allows you to import or export taxonomy from or to a CSV (comma-separated values) file or with a copy-and-paste text.

It helps you to quick import a non-standardized vocabulary, for example an old thesaurus, a hierarchical taxonomy or a simple list of children, synonyms, descriptions, weights or related terms to terms. It can be used as a module or as an API with a plug-in mechanism. It can manage internationalized vocabularies with i18n_taxonomy, a submodule of i18n module [Drupal 7 only].

Taxonomy CSV supports drush: you can import/export taxonomies from the command line interface with drush taxocsv-import and drush taxocsv-export.

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.

Important note

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.

Features:

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.

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.

Examples:

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.

You maintain page nodes for items like Terms of Service or Privacy Policy. These nodes appear on several sites and should always be the same.

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.

That is now possible by using OM Maximenu which can create menus with all other module blocks you want as attachments, modules like views, slideshow, menu, user, nice menus, quicktabs, and custom blocks with tables, lists, images, videos, etc.

Using the power of Feeds, almost any type of data can be imported into commerce entities, be it data in the Comma-Separated Values (CSV) format, XML format (use Feeds XPath Parser), or any other format for which a feeds importer exists. Data can also be synchronized from a remote location, e.g. from an XML or RSS feed, handling potential issues associated with duplicate content. Large amounts of data can be comfortably imported because of the Feeds usage of Drupal's core Batch API. This module can import both commerce entities and their associated commerce display nodes in two consecutive steps.

This module provides an API to shorten URLs via many services like bit.ly and TinyURL (over 15 services are available by default), as well as a block and a page that provide an interface for easily shortening URLs, and a block that displays a shortened URL for the current page for easy copying.

migrate_d2d provides a framework based on the Migrate API for migrating content from Drupal 5, Drupal 6, or Drupal 7 sites into the Drupal 7 site where it is installed. As of 7.x-2.1-rc1, it requires Migrate 7.x-2.6-rc2 or later. Besides addressing contemporary needs to migrate to Drupal 7, it has helped serve as a proof-of-concept for incorporating the migration approach into core as an upgrade path (https://groups.drupal.org/imp).

What this module does:

With Bulk Media Upload you can upload a bunch of files and a new node, taxonomy term, or other entity will be created for every file. The files are selected via a browser file upload dialog and can be stored in a file or image field.
Also default values can be chosen for the other fields assigned to the new node.