I tried enabling menu to import a site from d6, and 3 out of 6 of my menu elements were imported. I ran
update menu_links set customized=1 where menu_name="menu-ASDF"; on the database prior to reimporting and everything went smooth, all the menus got in.

I see in the code that the query in src/Plugin/migrate/source/MenuLink.php requires that customized=1, but old instances of drupal 6 will have some of the menus created by hand with customized=0. Maybe just point it out in the documentation on importation that this might be needed.

Comments

Guillaume Beaulieu created an issue. See original summary.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Component: menu system » migration system

Let's move to migrate, where it belongs more.

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Issue tags: +migrate-d6-d8
quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented

old instances of drupal 6 will have some of the menus created by hand with customized=0.

Will this be true even if the site has been updated to the latest minor version? I don't see anything that would update that field but I not very familiar with Drupal 6 or the menu system.

If yes, then this should probably be documented on the known issues page. However, if not, then there is no need to document because the general principle for a major version upgrade of a Drupal site, is that the source site is already upgraded to the latest minor version.

boran’s picture

boran CreditAttribution: boran commented

I also tried a D6 site import and the menu items did not show up on the D8 site.
Looking in the DB, customized is 1 for these entries (select link_path,link_title,customized from menu_links where menu_name like 'primary-links')
However it turned out that the menu is being pulled over (can be seen in admin/structure/menu/manage/primary-links), so one just had to place the primarylinks block in the right region and its shows up.
So, just mentioning this in case others go looking in the wrong place (DB) when their menu dont appear :-)

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Version: 8.0.1 » 8.1.x-dev

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

heddn’s picture

heddn
Primary language English
Location Nicaragua
CreditAttribution: heddn at MTech, LLC commented
Version: 8.3.x-dev » 8.4.x-dev
Status: Active » Closed (cannot reproduce)

Reviewed this in a our weekly migrate meeting. Upgrading to the most recent D6 is an expectation prior to migrating to D8. If someone can reproduce this, please re-open and provide some steps and versions.