migration

The Data Import/Export and Migration to Drupal groups are being merged together. Data Import/Export was devoted to one project in this area while Migrate to Drupal was started for more general discussion - what we're going to do is close the group now known as Migration to Drupal and alter the charter for Data Import/Export to be more general (this is the easiest way to handle it, since Data Import/Export has the larger membership).

If you are a member of Migration to Drupal, you should join Data Import/Export to stay involved.

Thanks.

Do you plan on including turn-key solutions for migrating from specific CMSes, e.g. Wordpress? Please see a discussion I've started elsewhere about how to handle improvements I've made to a related module that currently is not already on d.o. Ultimately I'd like to merge wp2drupal into a more general app but if Migrate isn't intended to be like that then there's no point. Thanks.

I've been updating the wp2drupal module and wanted to make the changes available to the greater audience via d.o. But my changes mark at least the fourth developer who's worked on it - it was originally created by Borek Bernard, then updated by someone by the name of teodorani (who used to own teodorani.com but which is no longer working), and then partially upgraded to D6 by DenRaf.

The Migrate module is already garnering some good feedback. My immediate plan is to stablize the current code base of V1 - please discuss ideas for further extension and refactoring here.

Thanks.

I pushed through with some of the changes I was making on monday, and implemented a mechanism for provision to conditionally include version specific code. What this means, is that 1 checkout of provision, will now have all the information it needs to manage any supported version of Drupal you throw at it.

I'm not a MySQL fun, so some troubles with MySQL database (MyISAM data corruption and too slow InnoDB) force migration of three existing Drupal 6 sites from MySQL to PostgreSQL. Since Drupal 6.2 some PgSQL-related bugs (sample) in core modules has been fixed, so I have a try.

Drupal 6.5 and PostgreSQL 8.3 compatibility

Drupal Core Modules

I've installed clean Drupal 6.5 on top of PostgreSQL 8.3.3 (with UTF8 database encoding) and played with it a lot. There is no heavy troubles, only minor ones:

I'm working on a migration path from the video module to the filefield module (using jQuery Media for playback). In terms of database language, I'm a Filemaker hack so I'm seriously struggling with many aspects of mysql, but I think I have laid out a good plan for attack and have a really good starting point to work from. I'm basically adapting a migration script that Moshe built for us at CCTV to migrate from the Image module to Imagefield.

Hey all, as I mentioned last night at the LA Drupal group I'm trying to move a Drupal install from a Windows XP box to a Linux box (Fedora Core 8). I'm working in the command line and I've done a mysqldump to a .sql file which I then move to the Fedora box. Both are running the same version of MySQL but as soon as I load the data into the database I get 404 errors when I try to hit the site.

As many of you mentioned last night there should be no issue in moving a database. I'm sure I'm doing something else wrong.

Thanks in advance for any thoughts.

Vaughn

From my inbox to yours...

Subject:    drupal consultant?
Date:   August 9, 2006 6:21:29 PM EDT
From:     mark@labornotes.org

Hi Noel,

I got your email from Linda Setchell at Eggplant Active Media. I work for a small non-profit in NYC called Labor Notes. We publish a monthly magazine for grassroots labor activists and have been working on redesigning our very old website to run on Drupal. We are almost done, but need to find someone who can help us take our site (which as far as I can tell is almost completely finished) and migrate it off the Eggplant test site and onto Site5 where we are going to host it. (The need kinda goes hand-in-hand with by Arthur Foelsche leaving Eggplant.)

I've been musing about the possibility of building a module for mass importing contents from existing sites, as an aid for migration to Drupal. I came across a potential model, an import utility for the CMS SAPID, http://sapid.sourceforge.net/en/doc/import/, code at http://prdownloads.sourceforge.net/sapid/migrator.tar.gz?download. The approach combines web crawling with regular expression-based data extraction. Users input the wrapping code patterns to search for, e.g., main content might be wrapped in and or maybe a div with a given class name.