Import and export

About

The WordPress XML for Feeds module exposes WordPress-specific data in WXR files (that's "WordPress eXtended RSS") to the Feeds module. It also includes the WordPress Importer module (a features-package), which imports WXR files using Feeds and the WordPress XML parser.

The purpose of the WordPress XML for Feeds (wp_feeds) and WordPress Importer (wp_feeds_wxr_importer) modules is to offer a comparable feature-set to the WordPress Import (wordpress_import) module (not to be confused with WordPress Importer (wp_feeds_wxr_importer) module), but in a way that is far more flexible, and that integrates with Feeds, CCK, FileField and other popular Drupal APIs so that data can be manipulated to fit arbitrary data models.

See also WordPress Migrate module, which I have not tried out. A comparison would be nice.

Features

Slideshare parser for the Feeds module. It uses SimpleXML for parsing so it doesn't require additional libraries, but I plan to add support for SimplePie parser in the future.

This module allows developers tracked by the CVS integration module to be associated with an e-mail address, to assist with the migration of CVS repositories to Git repositories. CVS Users will be associated with an anonymous "no-reply" by default. Additionally they will be able to select an e-mail from a list of addresses Drupal associates with the user.

This is a Drupal module that fetches and parses OAI_DC (Dublin core) metadata records from OAI-PMH services, as defined by http://www.openarchives.org/. It depends on the Feeds module.

Features

• Harvests from OAI-PMH repositories, respecting resumptionTokens, compression (but no deleted record support yet).
• Can map OAI_DC metadata into Feeds targets (CCK, taxonomy, etc.) (other metadata schemas can be supported by this or other modules in the future, today you can roll your own using existing modules)
• Can harvest from the entire repository or a single set. Available sets are loaded in via AHAH when creating the importer.
• You can set up multiple harvesting rules/mapping per set and/or repository as you desire.
• Record storage handled by Feeds: nodes (CCK support), raw database, etc. Extensible with other modules.
• Cron scheduling handled by Feeds: as often as every cron run up to a month between harvests.

Requirements

You need the Feeds module and its dependencies (Ctools, etc.) This module has been tested on Feeds 6.x-1.x-beta10.
Recommended additional modules: CCK, Link (to hold the resource URLs)

Usage

This module is for fairly advanced Drupal users. It helps manage database settings as they are shared between multiple developers, and also between dev, staging and live versions of a website.

Read the (verbose) introduction.

Be sure to read the README.txt before you enable and use the module! Once enabled:

a) There's a special copy of Drupal where the settings can be changed. It's called the "base".
b) Each table might contain settings and data. It uses database settings to reserve a range of IDs.

The site_update.module does some of the work for you. You have to remember to make settings changes on the special "base" copy of you site. And use a special script to "dump" those settings to a file. The file can then be treated like source code. So it can be checked into a version control system and shared among developers that way.

It is a little tricky to start using site_update on a site that already has a large database. It works best when you use it from the very beginning of every project. I highly recommend you give it a try on your next Drupal site.

Known problems and limitations include:

* The 2.x branch is close to being database agnostic. Primarily tested on mysql, but the goal is to work with any database.

wordpress_migrate supports migrating WordPress blog exports (WXR format) into Drupal using the Migrate module, which is now in