I am getting several "Source ID shortcut-set-1: Config entities can not be stubbed." messages from update/migrate from D7 to D8. D8 is at 8.1.8.

What does this message mean?

I found perhaps a related problem at https://www.drupal.org/node/2590993.

Do I need to worry about these messages?

Thanks!

Comments

samstamport created an issue. See original summary.

mikeryan’s picture

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

What this means is that the d7_shortcut migration attempted to resolve a shortcut's menu_name to a previously-migrated shortcut set, but the resolution failed. With content entities (nodes, terms, etc.) in this case it would create a "stub" to point to, but this can't be done for configuration entities like shortcut sets, so you get that message. Looking at how the shortcut migrations are set up, my best guess as to what would trigger this is if you had a menu_name in your D7 menu_links table like "shortcut-set-3" which did not exist in your D7 shortcut_set table - can you check and see if that might be the case?

The upshot of this, any shortcuts with unresolved shortcut sets will not be created in D8 by migration.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Postponed (maintainer needs more info)
samstamport’s picture

samstamport commented

shortcut_set table contains only one row with set_name = shortcut-set-1.

menu_links table contains five rows with menu_name = shortcut-set-1.
link_path contents are:
node/add
admin/content
admin/structure/taxonomy
admin/config/system/data_export_import
admin/config/system/backup_migrate/export/advanced

Please let me know if you need additional information.

samstamport’s picture

samstamport commented
Status: Postponed (maintainer needs more info) » Active

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.

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

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.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 Illinois
commented
Status: Active » Closed (outdated)

It's been a while since this was opened. Lots of things have changed since then. Perhaps this is fixed by various improvements in the overall migrate system?

fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Status: Closed (outdated) » Active

Still got this today on a 7.72->9.0.5 migration, so the issue is still there.

Same situation: on a site where no shortcut was created, the shortcut table only contains one row with "shortcut-set-1" / "Default".

JavierRodri1989’s picture

JavierRodri1989 commented

I also have these errors ... is it important for migration? there's a solution?

quietone’s picture

quietone commented
Status: Active » Closed (duplicate)
Related issues: +#3152943: Remove migration of shortcuts from menu_link migration

This is duplicate of a later issue which has a patch to fix this, #3152943: Remove migration of shortcuts from menu_link migration.

It would be very helpful if anyone experiencing this problem would try the patch in the other issue and comment there on the results. Thanks.

Closing as a duplicate.

oknaru’s picture

oknaru commented

I run D7.82 to D9.3.0 migration and also received "Source ID shortcut-set-1: Config entities can not be stubbed"