Path Management

Module that turns Drupal pager URLs into SEO-frendlier ones, like nodealias.html?page=0,2 to nodealias/page2.html.

this is the codebase for issue # 1091588

This module takes over the logout path and put a confirmation form and thus confirm with the user whether should logout or not.
Refer: http://drupal.org/node/1081098 (support request).

Overview

I had a discussion a couple of years ago about how to best create a Drupal front page that contains no content. That is, we want to build front pages that don't contain normal Drupal node-based content. Our front pages are made up of blocks instead.

This is a very simple module that provides a CTools access plugin for using the access rules of another path. It does nothing without the CTools module.

When creating a custom page with Page Manager (for example, a Panels page), this module adds the 'Access to another path' access plugin in the Access tab. You may use it to mirror the access rules used by another path. For example, you might set up a custom search page, and use the access rules for the default Drupal search page, 'search'.

Summary

Void menu allows you to configure special values to tags for use in the Drupal 7 menu system. You can customize up to 10 different void tags with any value you wish and use them freely inside the Drupal menu system.

Users can wreak havoc on a site by accidentally (or intentionally) creating a URL aliases which correspond to administrative or otherwise important URLs. (For example 'admin', 'sites', etc).

Default Persistent URL module is great, but sometimes simple features can become a hard task.
This module called "Duplicated path" comes to solve the problem which disables the ability to have the same path on different groups.
For example, you use Persistent URL with subdomain method to create "pseudo" minisite-per-group. Unfortunately, having an "about" page for each group just does not work.

The URL ID module provides a field that gives an entity a 'global' ID, based on the domain name, entity name and entity id (such as http://example.com/node/1).
The idea is that remote entities can be downloaded, inheriting the remote URL ID – a node could have the URL ID 'http://example2.com/node/123'.

For Drupal 7