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.Since menu links are not taking the path I planned and worked towards for D8, if #2227441: New plan, Phase 1:Review the architecture and overall implementation proposal for menu links as plugins happens, this needs to happen too.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 2237625.patch | 337 bytes | amateescu |
Comments
Comment #1
dawehnerI haz a sad :(
Comment #2
amateescu CreditAttribution: amateescu commentedMe too, but there are worse things in life..
Comment #3
pwolanin CreditAttribution: pwolanin commented@amateescu - so, I thought we were still largely going to be using your plan for content entities for the custom menu links. I've tried to update the summary on the #3 issue, but maybe we can discuss in more detail how we can make a system that meets all the apparent needs.
Comment #4
mgiffordOk, so looks like this needs to be done.
Comment #5
amateescu CreditAttribution: amateescu commentedYes, definitely. #2315773: Create a menu link field type/widget/formatter is the icing on the cake, instead of being able to use entity reference for menu items (+ even supporting tree revisions at some point) we now have to invent a whole new field type.
Comment #6
alexpottCommitted 2d4be0e and pushed to 8.0.x. Thanks @amateescu for the contributions to menu links in the D8 cycle. It's awesome that you're back in the issues making entity reference great.