[D8][UX] Merge Special Menu Items module functionality in core (allow <nolink> and <separator> menu items).

The module is already ported to Backdrop and is also used in backdropcms.org (to provide the special <nolink> path required for the "About Backdrop", "User Guide", "Developer Guide" and "Themer Guide" menu items of the Handbook menu).

This can be considered a sibling issue to #422 and is a sub-issue of #1839

GitHub Link:

https://github.com/backdrop/backdrop-issues/issues/1840

GitHub Issue #:

1840

Log in or register to post comments

Recent topics

custom module not showing up in modules list

Posted 3 days 4 hours ago by (ian) in How-To and Troubleshooting

TFA - how to setup fallback options 'per user'

Posted 3 days 20 hours ago by (clarkac) in How-To and Troubleshooting

Looking for examples of (local) news websites running on BackdropCMS

Posted 1 week 1 day ago by Erik Wesselius (zilvervos) in Other

Recent comments

As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...

Posted 3 days 9 min ago by (ian) on:

custom module not showing up in modules list

If you haven't already, flush all the caches. If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...

Posted 3 days 1 hour ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:

custom module not showing up in modules list

Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...

Posted 3 days 1 hour ago by (ian) on:

custom module not showing up in modules list