The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.With much humbleness, I wonder why the current migrate UI migrates everything but to 301 redirects...
What will a site owner do with say 100-1000 (or more) redirects made in Drupal 7 with Global Redirect from whatever reason?
I think we cannot except people to copy their redirections manually or to pay for such a customized solution...
I would personally glad to use such a feature. Will thank you for your opinions...
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | migrate_d7_redirects-2715807-16.patch | 15.72 KB | jofitz |
| #16 | interdiff.txt | 2.03 KB | jofitz |
Comments
Comment #2
berdirRedirect actually includes a migration template, I'm using this on one of our sites that we are updating from.
Maybe it needs some changes after the core changes in 8.1.0. But we have a test and that is working.
Comment #3
berdirAh, Drupal 7. I think there is currently only a migration for path_redirect for 6.x. You can look at that and implement a similar one for 7.x.
Comment #4
Benia commentedComment #5
jofitzCreated a patch for D7 -> D8 redirects migration.
(This will display a warning on /upgrade, but that is an issue with core, see #2569805: For Drupal migration, identify the source module).
Comment #6
ckaotikPlease declare the dependency on migrate_drupal and the path_redirect module being present in the source installation in the annotation, see #2744721: Migration Templates depend on migrate_drupal.
Comment #7
jofitzAdded tests for d7 migration (and a few missing newlines at ends of files).
Comment #8
jofitzAdded changes recommended by @ckaotik - test failure expected.
Comment #11
jofitzIssue now on hold because it depends on the patch in #2560795: Source plugins have a hidden dependency on migrate_drupal.
Comment #12
mikeryanComment #14
jofitzHandle status codes of 0 (i.e. default status codes).
Comment #15
jofitzAdded status code check to tests and general readability improvements.
Corrected source_provider and made necessary additions to test fixtures so that it now passes tests.
Comment #16
jofitzAdded Unit test to redirect migration.
Comment #17
manu manuWorks well for me, thanks for working on this.
Comment #18
berdirLooks good, has tests and has been tested manually. Sounds like this is ready.
Comment #19
jofitzWhat do we need to do to get this committed?
Comment #20
G42 commentedI have tried this patch on the dev and alpha versions and the Drupal migrate UI keeps registering Redirect migration as missing. Can you provide details on how you got this patch to work?
Comment #21
berdir> What do we need to do to get this committed?
A maintainer ;)
Which I am, as of today.
Committed, thanks for your work.
@G42: If you haven't figured it out yet, I suggest you open a new issue.
Comment #23
jofitzThanks, @Berdir
Comment #25
heddnLinking in #2906878: [Meta] Support for D7 -> D9 contrib migrate
Comment #26
drupalninja99 commentedMy question is how come this doesn't get pulled in by drush migrate:upgrade? Is there an extra bit of code required to allow this to be discovered by upgrade? For now I have manually copied the d7 migrate yml to my config folder.