1. sub urls of node and user will be rewritten when the parent url has an alias.
2. you can use regex to rewrite any url if you want
NOTICE: no need to enable this module, just include the core in your settings.php
This module adds a new field to menu items to set a subtitle to show on menu links!
Actualy it should work on primary/secondary menu and normal menu items.
TODO:#show the subtitle above the menu link as option
#generate the subtitle with custom php code
#integration with views
#integration with token
KNOW BUGS:1. This module breaks Context module UI configruation
2. This module stops theme_menu_link() hooks from being run at the theme layer
Integration of the "organisational directories" and the taxonomy module.
Each directory becomes a custom taxonomy term with the path as field.
Allows for the user to 'turn on' a menu for given content types via the menu edit form.
The Easy Breadcrumb module provides a plug-and-play block to be embedded in your pages, typically at some place near the page's header. Easy Breadcrumb takes advantage of the work you've already done for generating your paths' alias, while it naturally encourages the creation of semantic and consistent paths. This modules is currently available for Drupal 7 and 8.
Allows menu items to render views instead of links. This is useful for creating "mega-menus".
Menu Views is a utility module. It provides back end support for replacing a standard menu item link with a menu item view. Menu items (in any menu) now have the option of toggling between two different menu item types: link or view. Depending on which option is selected, the appropriate configuration form is displayed on the admin side and the appropriate type of item is rendered on the front-end.
Menu Views is NOT a theming/styling module for mega-menus. As stated above, this module is strictly a utility module for replacing menu item link with a view. Once the HTML markup is there, Menu View's job is done! Read #1794010: Menu Views is not working.
Depending on how a theme renders the primary and secondary navigation, this module may not work because the parent items may not ever be extended (regardless whether they are checked as such in the menu item).
It is strongly recommended to use one of the following modules in your theme's menu region instead (see: Use menus in Drupal 7? You need Menu block module.).
Born out of frustration with existing breadcrumb projects, here's yet another breadcrumbs API.
The architectural design is based on the Crumbs module and References hierarchy (sandbox; works with Menu position).
This is the version 2 development of OM Maximenu, it will take advantage of the new api features of Drupal 7, and this will only for Drupal 7 and up.
Some sites use the boxes module, but other modules in the site may depend on Drupal's core blocks module. When using context for placing boxes it becomes confusing for users to see the blocks menu item and associated admin UI.
Kill Blocks removes most of the blocks UI while still allowing the boxes UI to function properly.
This is a work in progress. Right now it is impossible to delete a box via the UI.
Drupal's regular menu system administration doesn't scale very well. This is due to the fact that for all node edit pages, node type edit pages and vocabulary edit pages (when Taxonomy Menu is active), Drupal loads all menu items from all menus in the system. For large amount of menu items, this slows down the system to an unusably slow speed, or even causes timeouts.
This is a known problem in Drupal core. This comment is from the menu module:
