Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By Mikael Berger on
As you probably know, the blog content type has been moved out of Drupal 8 core. There is Blog module that replicates the blog functionality. However, somewhere along the way it was decided to change the content type machine name. D7 core blog uses "blog" whilst the contributed module uses "blog_post".
Linguistic considerations apart, the altered machine name is an obstacle for an otherwise straightforward migration procedure for legacy D7 blogs. So, I tried just to pick the Blog module code and substitute "blog_post" for "blog" in all files and also the module's file names. At first glance, it Works like charm, all my multi-user content is there and can be managed just as in D7. More importantly, i did not have to fiddle with any D8 migration paths or templates, I just installed the module before upgrading.
I would strongly suggest that our community puts order in this. Otherwise, sooner or later somebody would create a "Legacy Blog" module and yet again the Drupal initiative would fork into duplicated code and multiple maintenance efforts. There are currently 348 sites using the module and 6,529 downloads. Therefore I suppose the least damage would be to focus on the still not migrated D6 and D7 sites. That is, to revert the machine name back to "blog".
Comments
=-=
This is something that should be raised as an issue (if it isn't already) in the core issue queue.