Import/Export

Introduction

This module provides for the ability to synchronize content of nodes on the site with external source, typically a subversion repository. The text is stored in the svn repository in Writeup format and processing is done only when the content is imported from svn rather than by means of an input filter (as with the writeup project).

A Drupal 6 version is expected to be fully working by the end of March 2012, and a Drupal 7 version by the end of May.

The NodePorter Exporter and NodePorter Importer modules work hand-in-hand to export nodes to an XML description or import nodes from an XML description.

These modules can be used to programatically import content from other systems and data sources or export content and import it into other Drupal sites.

NodePorter uses the FieldTool module in Drupal 6 to export CCK types.

See the NodePorter documentation for more details.

The MMPorter Importer and MMPorter Exporter modules extend the NodePorter modules to allow exporting Monster Menus page hierarchies and permissions to an XML description or import Monster Menus page hierarchies and permissions in addition to node content.

See the MMPorter documentation for more details.

Context Export builds on the Context module to provide simplified exports. Contexts can be exported automatically (or manually via a single link at /admin/structure/context) and provided as "default" contexts, which makes Context changes easily transferrable between development environments via a version control system.

This module extends Disqus module by adding an option to export Disqus comments into an XML file that Disqus supports.

Simple client/server module to share rendered blocks across different Drupal sites. Must be enabled on both sides.

Usage:

Server side:

• Go to /admin/config/system/distributed_blocks and check 'This site exposes its blocks for sharing'.
• Under exposed blocks, select those you would like to share with other sites.
• Save the settings.

Client side:

This is an integration module for monster_menus and millennium, the library catalog module. The purpose is to ensure that nodes created by the millennium module are mapped to specific Monster Menus pages. This is exposed to the user by allowing people using the batch import process in the millennium module to enter a Monster Menus Tree ID in the configuration form.

Future development tasks:

This module provides integration between the feeds and monster_menus modules. Specifically, it adds the Monster Menus Node Processor to Feeds, based on the Node Processor that adds a single additional field to the configuration form allowing the administrator to enter a Monster Menus Tree ID where all the nodes imported by the Feeds processor will be placed.

Provides an intermediary Feeds Processor class that allows you to store imported items in a queue for reviewing them before import.

This module adds support for importing data through Feeds into translatable fields handled by Entity Translation.

The module exposes fields that are translatable into all enabled languages, enabling the creation of translations of entities when importing.