Problem/Motivation

The module features are not available on menu items that are provided by custom module (or core modules).

Steps to reproduce

- Spin up Drupal 9 site with standard install profile (https://simplytest.me/)
- Install Menu Link Modal
- Navigate to the Menu UI (Structure > Menus)
- Edit the Tools menu
- Add a link ("Test", , Open link in modal) to verify the module works
- Edit the existing "Add content" item
- Observe notice that the menu item is provided by Node module, and that the Modal Settings fieldset is not available

We are experiencing the same issue with module provided menu links in custom modules.

Proposed resolution

Remaining tasks

User interface changes

Original post

this only appears to work for menu items added after the module was enabled is that as designed?

it would be great to enable modal on pre-existing menu items.

thanks

Comments

laurencefass created an issue. See original summary.

miteshmap’s picture

miteshmap
Primary language Gujarati
commented

No, It is designed to work with existing menu as well. Can you attach screenshot of configurations and any console error if you are facing?

DrupalDan’s picture

DrupalDan commented

I think I followed the steps but it seems that its not working. After I saved the menu and clicked on the link I just ticked "Open link in Modal", there was no modal effect and the page just shows as it used to be.

miteshmap’s picture

miteshmap
Primary language Gujarati
commented
Status: Active » Postponed (maintainer needs more info)

there could be an issue with js, Does your console show any error? if not it should work fine: check this Comment

jason.bell’s picture

jason.bell commented
Title: doesnt work for existing menu items » Modal settings fieldset is not available on module provided menu items
Version: 8.x-1.x-dev » 8.x-2.0
Category: Support request » Bug report
Issue summary: View changes

In testing this module for possible use, I came across this existing issue report. I have updated the summary with more information since it appears to be an open issue, at least in Drupal 9 builds.