- Issue created by @undersound3
- 🇧🇪Belgium andreasderijcke Antwerpen / Gent
Surprised to find out this works without issue.
Just need to find a why make this configurable :D
- 🇺🇸United States joewhitsitt Iowa
An issue we have run into in doing this is if we have a media matcher that we want to run through the substitution "Direct URL to media file entity" which only seems to trigger when used with the linkit formatter. This doesn't seem to trigger when superfish, menu blocks, etc. are calling the stored link value directly. We are instead thinking about creating a separate linkit profile without the media matcher so we can still move forward with this.
- First commit to issue fork.
- Status changed to Closed: works as designed
about 2 months ago 7:22pm 27 June 2025 - 🇺🇸United States mark_fullmer Tucson
I think the custom code suggested in this issue is the right way to go, short of a new UI setting that would allow sites to enable Linkit for the menu link UI and to configure which Linkit profile should be used for that. My hope is that the forthcoming core solution in ✨ Drastically improve Drupal's default linking experience in text fields Needs work will support menu links, and that there will be no need for this to be provided in contributed code. So, for now, I think this should not be added to Linkit itself.
We are instead thinking about creating a separate linkit profile without the media matcher so we can still move forward with this.
That sounds like a reasonable approach. I don't think it's likely that there would be a need for a media matcher to be used in Drupal menus, so I'm disinclined to complexify the code by somehow modifying the rendering of menu links (beyond just the autocomplete selection provided by Linkit).
- 🇧🇪Belgium andreasderijcke Antwerpen / Gent
In our case, we also used a dedicated linkit profile, not only to exclude Media but also to limit to certain node types and vocabularies.
I understand the choice not to support this as a feature, but perhaps this can be mentioned in the README as a 'use at your own risk' as I think it is very usefull towards content editors?
- 🇺🇸United States mark_fullmer Tucson
perhaps this can be mentioned in the README as a 'use at your own risk' as I think it is very usefull towards content editors?
Excellent suggestion. I've added a new documentation page at https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →