See also #1017246: UI for running migrations. It would be nice to have an interactive means of defining field mappings for migrations - most likely we would do this with features and/or CTools integration.

CommentFileSizeAuthor
#24 MigrateUI.png38.55 KBklonos

Comments

seandunaway’s picture

seandunaway commented

+1!

manoloka’s picture

manoloka commented

subscribe

geerlingguy’s picture

geerlingguy commented

Subscribe. Makes things oh-so-much quicker for the simpler things in life.

dynamicdan’s picture

dynamicdan commented

Subscribe. I'm currently considering 4 options for importing content. A GUI would be the deal breaker.

yesct’s picture

yesct commented

I can test patches.

chadchandler’s picture

chadchandler commented

Absolutely. I feel guilty asking for anything else to be added to this wonderful module, but if I had to .. a UI would be even more amazing. Great work, people!

dynamicdan’s picture

dynamicdan commented

BTW, I've switched to Feeds because of the GUI. It works as desired. I would suggest you discuss options for merging the modules to save on dev resources and create something that could one day be in the drupal core... "Import your data" option = the dream.

As a side note, I can't use drush on my production server (CLI mysql access disabled for security reasons) which would mean this module was never an option.

Fidelix’s picture

Fidelix commented

Subscribing...

ijf8090’s picture

ijf8090 commented

Me too please....

Great module BTW.

wiremuse’s picture

wiremuse commented

This would be great for 7.x & 6.x

anil614sagar’s picture

anil614sagar commented

Subscribing + 1

eileenmcnaughton’s picture

eileenmcnaughton commented

subscribing

sylus’s picture

sylus commented

subscribe

vacilando’s picture

vacilando commented

+1

spessex’s picture

spessex commented

subscribe

Fidelix’s picture

Fidelix commented

spessex, you don't have to subscribe anymore.
Use the "Follow" button on the top of the issue.

cdracars’s picture

cdracars commented

Are there any plans on making this happen still?

mikeryan’s picture

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

No concrete plans - it'd be nice to do someday, but unless someone out there is planning on contributing a patch, I wouldn't hold my breath.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Assigned: Unassigned » mikeryan

As part of the Drupal-to-Drupal migration project, I'm starting work on a wizard-based UI to prompt for details on the source system and mappings from sources to destinations, which at its end will generate the migration classes ready to run. Meanwhile, the number of options in WordPress Migrate is getting a little out-of-hand to all do on one page - it should have a similar wizard process.

So, what I want to do is build the infrastructure into migrate_ui to allow source-specific migration modules to plug in some settings and any application-specific form definitions, letting migrate_ui handle the wizards and migration registration. My current plan is that any such module would implement hook_migrate_ui_wizard(), returning a configuration array (whether it supports migrating users, a form for gathering credentials for the source data, etc.). If this hook is implemented by any module, migrate_ui will present a form allowing you to choose your import source (WordPress, Drupal, etc.) and launch a source-specific wizard.

This won't be a completely general answer to this issue, but will provide a solution for particular sources, and if someone decides to implement such a module with Views as the source, we would pretty much have the old Migrate V1 capability...

alexeyal1’s picture

alexeyal1
Primary language Russian
commented

+1 Это сильно расширит аудиторию модуля!

mikeryan’s picture

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

I've opened up an issue at #1826112: Wizard framework. That won't produce a full general-purpose UI, but will be a major step in that direction.

mikeryan’s picture

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

With Migrate 2.6, we now have a field mapping editor, plus the wizard API for building UIs to define migrations from particular sources. More work could certainly be done to build on this, but the basics are now there and any follow-ups should be in distinct issues.

mgifford’s picture

mgifford
he/him
Primary language English
commented

What's the ETA on a 2.6 release?

Never mind, just saw the beta link in the project description. Wasn't where I was expecting it!

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Component: migrate_ui » Documentation
Assigned: mikeryan » Unassigned
Category: feature » task
Status: Fixed » Active
StatusFileSize
new MigrateUI.png38.55 KB

...here's a screenshot for the project page.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Component: Documentation » migrate_ui
Category: task » feature
Status: Active » Fixed

Restoring issue status. That screenshot appears to be from Migrate 2.5. At any rate, if I decide to add screenshots to the project page I can easily do that myself.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

Yeah, sorry. Didn't mean to upset you there. It just happens that whenever I file a request for a screenshot for other projects either the maintainer(s) ask to provide one (due to lack of time) or if no one does that beforehand, it takes a long time before the screenshot is actually added.

I took the screenshot from simplytest.me and it currently does not allow selecting versions for contrib modules. So, yeah it's 2.5 since that one is listed as the recommended version on the project page and my guess is simplytest.me just picks that one up.

As to why to request adding a screenshot in the first place (from the project's page):

...The main theme of this release is UX - the existing UI has been significantly rearranged, ...

Well this is really vague for both newcomers (that don't know what the module's UI looks like) and the ones using previous versions of the module seeking to upgrade (do they need/like the new UI?). A pretty screenshot would be perfect.

Oh well, once again sorry for upsetting you, but please consider that I did spend some of my almost non-existing spare time to give the module a spin and take the screenshot

mikeryan’s picture

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

I'm sorry if I seemed "upset", I didn't mean to come off testy. Requests to change the project page should be distinct issues, not done by reopening a closed issue (that's the point that was a bit annoying).

Although the UX has been enhanced in this version, Migrate itself is still primarily a framework - the UI is secondary, and I don't want to emphasize it too much. The big news with this release is actually the framework that enables other modules like WordPress Migrate to provide simple UIs for imports, and screenshots on the project page make more sense in those cases.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

Don't worry about it Mike. We all have bad days ;)

Thanx for the time you spend on maintaining this project.

Status: Fixed » Closed (fixed)

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