Where are the redirects?

Hi @dawnrae,

The redirects are handled within the plugin itself. You should leave the plugin active after the migration and it will quietly handle the redirects for you in the background.

Hmmm, I’m not sure I like that. The plugin is serving no other purpose at this point than that. If the plugin is deleted, does it remove that information from the databsase? Is there a way to export them out to use them within the .htaccess file?

Technically it will be possible to setup similar redirects via htaccess. However, this will only work under certain circumstances.

In Blogger, multiple blog posts can have the same slug. For example, the following is possible:

https://example.com/2019/03/blog-post-slug.html
https://example.com/2020/05/blog-post-slug.html

However, this same structure is not possible in WordPress as two posts cannot have the same slug, even if they are posted in different months. WordPress will change the links to:

https://example.com/2019/03/blog-post-slug.html
https://example.com/2020/05/blog-post-slug-2.html

To make sure that’s handled, the full Blogger permalink is added to each post as meta data. This data is not lost if you uninstall the plugin, however the plugin is needed to handle the redirect itself. When an old Blogger link is hit and does not exist in WordPress, the plugin searches for the post with matching meta data and then serves the new permalink.

If you don’t have too many posts, or know that posts won’t have the same slug, then you can certainly setup some htaccess rewrite rules instead. It will need to handle link structures for posts, pages, labels, archives and RSS feeds for full effect.

That said, keeping the plugin installed shouldn’t cause any issues. It is very light and won’t slow anything down. I do understand where you’re coming from though, I prefer to keep my plugins list as clean as possible too.

Hope that helps,

Phil

• This reply was modified 4 years, 10 months ago by pipdig.