To help support #1826134: Support new Migrate wizard framework, and to clean things up in general, there's some refactoring I'd like to address for the next version of WordPress Migrate after 2.1 is out. We need to separate out the preprocessing of the WXR file to a separate file to make it reusable. The use of variables for configuring the migration should give way to per-migration arguments, right now if you import multiple blogs with different options you can get things confused. And there are any number of smaller cleanups that don't come to mind immediately...

Comments

jpstrikesback’s picture

jpstrikesback commented

The use of variables for configuring the migration should give way to per-migration arguments, right now if you import multiple blogs with different options you can get things confused.

Is there a current workaround for this?

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

No, this is the issue which will address it.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

I should ask, are you actually having an issue with this today? It would only be a problem if you were rerunning migrations through the regular Migrate dashboard after initial import... I.e., you import one blog with the tag vocabulary set to tags, then import another one with the tag vocabulary set to categories, then went to the dashboard and rolled back and reimported the first one, it would import tags to the categories vocabulary.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

The main portion of this work is done and committed to the wizard_api branch - it needs more testing, but if you're in a hurry you can pull that. It'll get merged into 7.x-2.x after 2.1 is released.

jpstrikesback’s picture

jpstrikesback commented

Just heading to dinner but I'll test later tonight, I have 3 separate blogs to import to one site, some go to different content types so that's why I'm interested. I'm also hosting on pantheon and I cannot use the UI (only drush) tho I saw some commits that speak of forcing drush and hinted at background processing...

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Fixed

I don't think any more refactoring needs to be done under this issue, any specific work to be done for 2.2 should go into its own issue (like #1840730: Fix attachment fields for next release).

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.