The d7_menu_links migration complains about failed path validation for many links.
The reason: it points to content entities that have not yet been migrated. Its migration dependencies are:
migration_dependencies:
required:
- d7_menu
While this guarantees the existence of the menu in which a migrated menu link lives, it does not guarantee that the location the menu link points to exists. This is the problem.
None.
None.
None.
TBD
Needs work
10.1 ✨
It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Rerolling for 9.5.5. (#67 still applied fine to 9.5.2.)
🐛
Remove migration of shortcuts from menu_link migration
Fixed
conflicted with this in \Drupal\menu_link_content\Plugin\migrate\source\MenuLink. This patch already had the logic that that added in D7MenuLinkDeriverTrait::getBaseQuery().
(See #11.)