Something wrong in descripton there: https://www.drupal.org/project/special_menu_items. To work with nolink must add route:<nolink> to link instead <nolink>

Comments

csikosz created an issue. See original summary.

csikosz’s picture

Issue summary: View changes
devil2005’s picture

doesn't work either :(

dqd’s picture

Title: Nolink description » <nolink> info on project page is misleading - status unclear
Priority: Normal » Major

This isn't fully supported in core yet Error: Manually entered paths should start with /, ? or #. if simply entered <nolink> and broken sub menu items in toolbar when using route:<nolink> which indeed works (functionality only but without theme implementation). The project page information is half wrong/incorrect since it conveys the core support is 100% done. And IF this will be ever 100% in core like it was supported by this module, seems unclear yet, so we rather should set this module up to "be ported to D8" until this is clear (new D8 Porttracker issue). If the maintainer has no interest in porting the project, the page should be set to "seeking for co-maintainer" instead of stating the core support which isn'T completed. And an issue should be opened to discuss a maintainer for the D8 version of this project.

If the status of core changes the module can be checked for being an additional feature provider (core modules often are very feature limited) or can be marked as duplicate with a link the core feature then.

jmuzz’s picture

Yes these links do break when you try to use them in the toolbar module. I don't think this is an issue with route:<nolink> though and I'm not sure that any linkless menu item that another module puts in it would work any better.

IMO it should be a bugfix for the toolbar module.

As far as I know route:<nolink> itself is working correctly.

Personally I have worked around it by making a page at /admin/dummy to point all my parent toolbar items to. It's not ideal, but it fixes the theme issue at least.

sopranos’s picture

yes Csikosz is 100% right....why dont you update your module home page???

route: is correct

using DOES NOT WORK

portulaca’s picture

Status: Active » Closed (duplicate)
Related issues: +#2927991: Correct info on project page about D8 functionality