Not sure if this is more of "documentation opportunity" than a bug, but I figured I'd throw it out there and find out.

During my D6->D8 migration testing, I noticed that "story" nodes on D6 (one of the default D6 content types) were migrated into a new "story" content type on D8, not the default "article" content type on D8.

I understand why this happens, but I'm wondering if it should happen. I think most people would expect D6 story nodes to be migrated to D8 article nodes, right?

-mike

Comments

ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented
Title: Importing "story" nodes from D6 creates new content type in D8 » Migrating "story" nodes from D6 creates new content type in D8
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

I think the behavior is correct - we should preserve the content types from D6 as they are, I don't think the fact that the standard D6 profile had a 'story' content type and D7/D8 standard profiles have an 'article' content type means that we must assume the content type name should change in migration. Note that the D6->D7 upgrade process does not alter story content to become articles.

ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented
Component: Code » Documentation

@mikeryan,

That makes sense - I think we just need to be sure we document this somewhere so users understand it is intentional.

-mike

ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented
Project: IMP » Drupal core
Version: » 8.x-dev
Component: Documentation » migration system
Issue tags: +Needs documentation, +Novice
star-szr’s picture

star-szr
he/him
Primary language English
commented

Document where? This needs a clearer starting point for it to be a good novice issue IMO :)

star-szr’s picture

star-szr
he/him
Primary language English
commented
Issue tags: +Documentation
ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented

That's a great question - one I don't have a clear answer for. Migrate documentation is mainly developer-centric at this point, but I think we need to add a "what to expect" type of section with details like this one...

-mike

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed

I have added this to Known issues with the Drupal 6 -> 8 migrate path and modified it to not be simply "excluded" items, but simply a generic "known issues" for D6->D8.

Updated the tags on that page to target the appropriate audiences. While I was at it I added a note about Views being a core component that will not be migrated within the core package.

Status: Fixed » Closed (fixed)

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