I lack documentation on how to perform such a basic migration, unfortunately I cannot find options that would allow me to do so.

On my part, I have installed all the required modules and no errors are visible.
Maybe it is because I am working on Drupal 11?

Comments

tczaude created an issue. See original summary.

ressa’s picture

If you need something simpler, maybe check out this module?

https://www.drupal.org/project/wordpress_migrate

tczaude’s picture

Hey thanks, this module is for d10 that you sent me, that's why I rejected it.
I don't know, somewhere in my head I'm missing some image for this module.
I don't know, out of desperation I'm inclined to write a python script for API for this :/ But for now it's a project like proffOdConcept, that's why I'm looking for something in the simplest version

ressa’s picture

Perhaps use Drupal 10, if possible?

tczaude’s picture

I'll figure out how to use this module. I'll find a solution, sorry for bothering you.

ressa’s picture

No problem, good luck with the project!

salvatoren 🇮🇹’s picture

I'm here for same reason.
WP to drupall 11 CMS.

Tried with wordpress migrate, but not work as expected.

Tried this, cannot found any way to use.

Any help is more appreciated.

Ty

omarlopesino’s picture

Assigned: Unassigned » omarlopesino

Sorry for the late response.

The module uses Migrate APÎ framework documented here: https://www.drupal.org/docs/drupal-apis/migrate-api/migrate-api-overview . Knowing how it works allows to start creating migrations of content from worrdpress to Drupal

However , I agree that it is necessary documenting how to perform a wordpress migration, as for most of the cases the steps to follow are identical. And, it will make the module easy to use for those who need migrate Drupal to Wordpress.

I will work ASAP by extending the README.md and the module description to explain the steps to follow. Also , I will include an examples folder with the most common migrations so they can be easily copy-pasted.

ressa’s picture

Thank you @omarlopesino, that sounds wonderful, more documentation makes everything much easier for everyone!

I don't use WordPress, so I created the page https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... a while ago, to get some test content.

Feel free to link to it from the extended WordPress Migrate SQL README.md. If you plan to add documentation for migrating content not included in the "How to generate WordPress content ..." doc page, feel free to add the steps, if possible :)

Or, if you describe it here, I can add it to the doc "How to generate ..." page.

  • omarlopesino committed 4c43e40b on 1.x
    Issue #3509156: Update README with additional documentation and similar...

  • omarlopesino committed 66da4933 on 1.x
    Issue #3509156: Explain that wordpress database must be accesible
    
omarlopesino’s picture

Status: Active » Fixed

I have created a 1.0.0 version with these changes:

  • Now the module description is updated, and links to README files that explains how to use the module.
  • There exists a new submodule named wordpress migrate SQL basic that allows migrating from the UI without needing to code. This is also documented in a README file. It provides migrations for articles, users,
  • There exists a drush generate command that allows scaffolding these migrations, for those who need to customize the migration.
  • There are tests for all the source and migrate process plugins.
  • I've added into documentation the link to generate test content, many thanks @ressa!

Hope this helps to make this module easier to use for plug and play use cases and for developers who need a customized migration.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

ressa’s picture

Version: 1.0.0-alpha14 » 1.0.x-dev

Very nice, thanks @omarlopesino!

I notice now that there is an easy solution available as well, which may get overlooked. I did not catch it, and many may overlook it, if they just skim the top of the page and see "recommended for complex WordPress sites" and "pure SQL source over WXR exports."

So perhaps consider squeezing in a sentence like this at the top of the project page and README?

WordPress Migrate SQL lets you build migrations from a WordPress site's MySQL/MariaDB database straight into Drupal. It's recommended for complex WordPress sites and for people who prefer a pure SQL source over WXR exports.

It also offers a ready-to-use migration for common WordPress content and a page to import or roll them back, with not need to write code.
^^ add this?

Full setup and usage instructions are in the module's README.md.

omarlopesino’s picture

Nice suggestion, I've added that additional phrase to let anyone understand quickly this module offers a ready-to-go solution. Thanks!

ressa’s picture

Thank you, it looks great! Should the sentence also be included in the README intro text?

PS. On the project page, we could link to one of these? (or not, if you think the link to the general README is enough)

  • omarlopesino committed 43346b28 on 1.x
    Issue #3509156: More brief explanation of the Zero code approach
    
omarlopesino’s picture

Issue tags: -Needs documentation

I've refined both sections to be more brief. I think we can keep it as it is and if there are new people confused about how to use the module we can refine it with their feedback.

  • omarlopesino committed 43346b28 on 1.0.x
    Issue #3509156: More brief explanation of the Zero code approach
    

  • omarlopesino committed 66da4933 on 1.0.x
    Issue #3509156: Explain that wordpress database must be accesible
    

  • omarlopesino committed 4c43e40b on 1.0.x
    Issue #3509156: Update README with additional documentation and similar...

  • omarlopesino committed 459649b6 on 1.0.x
    Issue #3509156: Make the module easier to use and well documented
    
    This...

Status: Fixed » Closed (fixed)

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