0

Drupal 7 to 8 Migration works only on the core, thus doesn't inlcude 301 redirects created in D7 with the Global redirect module.

Is there a workaround to migrate all the 301 redirects to Drupal 8 instead of coping them manually (after the site itself migrated successfully from D7 to D8) ?

The reason I ask this is because if I won't migrate these redirects, search engines that already indexed the old paths, will show 404's and these pages' SEO will most likely damage.

1
+150

The Global Redirect module doesn't store paths on a per-node basis. That's the role of the core path module which stores aliases that map to system paths in the url_alias table (in both D7/D8).

The Global Redirect module could broadly described as settings (set on its administration page) that drive logic for 301 redirecting (in a hook_init() invocation) while setting the rel="canonical" metatag (a signal that tells the search engine to index that path). Thus, there really isn't anything to migrate from the module besides various globalredirect_settings variables that store redirect settings.

That said, you can run the Migration module which will import your node path aliases (and thus the paths you're concerned with 301 redirecting to) and adjusting the settings for Global Redirect module so that it matches the settings in your D7 installation.

5
  • Shawn, I've read your answer twice and I think I might miss something (I also edited my question in relation to that). I can't understand how it is that the migration UI will also migrate old paths that are being accessed from search engines in this very moment - I keep wondering where will it take that data from, given that the "Redirect" module, which is not GRD off course, is also not part of the core and thus also not a part of the migration process.
    – user16289
    May 2 '16 at 6:08
  • 1
    I've updated the answered with elaboration on your 2 issues with paths & SEO. The migration module is importing in path aliases from the Path module. The Global Redirect module is signaling to search engines through canonical metatag it sets. Thus, if both the D7/D8 modules are setting the same canonical metatag & the migration module has imported in the same aliased canonical path, a search engine should see that the same content is there.
    – Shawn Conn
    May 2 '16 at 7:14
  • Thank you Shawn for your elaboration. I do wonder how it relates to what Berdir said in the following link about migration path for the redirect module itself (or there is no real connection between the 2): drupal.org/node/2715807#comment-11149059
    – user16289
    May 3 '16 at 5:51
  • @Benia that discussion with Berdir is in regards to the Redirect module and not the Global Redirect module.
    – No Sssweat
    May 4 '16 at 5:42
  • The question mentions GRD and associates it with migration to the Drupal 8 Redirect module. Maybe you meant to say that the migration path Berdir talked about is only from Redirect 2 Redirect, and in any case it won't do anything with GRD?
    – user16289
    May 4 '16 at 6:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy