Path Management

Work in progress for a Drupal 7 integration and collaboration between redirection-type modules:

• Path redirect
• Global redirect (Merged in basic functionalty: #905914: Merge global redirect functions into Redirect module)

Current features:

• Common API for loading, saving, and deleting redirects.
• Case-insensitive redirect matching with a hook to allow other modules to narrow-down the candidate redirects.
• Redirect counter and last used timestamp, with automatic cleanup of inactive redirects.
• Integration with Drupal's page cache to optimize redirects and performance.
• Complete individual redirect access API.
• Views API integration.

This project implements a filter framework for easier creation of HTML links to other pages on the site or to external sites.

The framework uses a wiki style format such as [[indicator:target]] as markup to identify links. For example: [[nodetitle:Page One]] becomes:

Module description

The link module provides a standard custom content field for links. With this module, links can be easily added to any content types and profiles and include advanced validating and different ways of storing internal or external links and URLs. It also supports additional link text title, site wide tokens for titles and title attributes, target attributes, css class attribution, static repeating values, input conversion, and many more.

This module allows you to specify a redirect from one path to another path or an external URL, using any HTTP redirect status.

#D7CX: I pledge that Path redirect will have a full Drupal 7 release on the day that Drupal 7 is released. Note that the project has moved to http://drupal.org/project/redirect for Drupal 7.

Update: For Drupal 8 please use the redirect module. This project is deprecated for D8

What?

GlobalRedirect is a simple module which…

1. Checks the current URL for an alias and does a 301 redirect to it if it is not being used.
2. Checks the current URL for a trailing slash, removes it if present and repeats check 1 with the new request.
3. Checks if the current URL is the same as the site_frontpage and redirects to the frontpage if there is a match.
4. Checks if the Clean URLs feature is enabled and then checks the current URL is being accessed using the clean method rather than the 'unclean' method.
5. Checks access to the URL. If the user does not have access to the path, then no redirects are done. This helps avoid exposing private aliased node's.
6. Make sure the case of the URL being accessed is the same as the one set by the author/administrator. For example, if you set the alias "articles/cake-making" to node/123, then the user can access the alias with any combination of case.
7. Most of the above options are configurable in the settings page. In Drupal 5 you can access this after enabling the globalredirect_admin module. In Drupal 6, the settings page is bundled into the module.

Custom Breadcrumbs 2 (6.x-2.x and 7.x-2.x)

Many new features have been added including support for Views, Panels, Taxonomy vocabularies and terms, paths, and a simple API that allows contributed modules to enable custom breadcrumbs for module pages and theme templates. These are implemented using optional, independent submodules that depend on the main Custom Breadcrumbs module.

In addition to breadcrumb visibility, this version provides an option permitting PHP code snippets to be used in forming the breadcrumb titles and paths. Multiple languages are also supported.

Node Hierarchy allows nodes to be children of other nodes creating a tree-like hierarchy of content. The module offers:

• 1-Click creation of hierarchical menus
• Hierarchical breadcrumbs
• Automatic hierarchical urls using Pathauto (and token module)
  (eg: q=aboutus/history/beginning).
• Automatic creation of hierarchical menus if desired.
• Optional Views integration.
• Optional Node Access integration.

Easily create subdomains per user, taxonomy term, content type, or organic group. This module adds an easy text field to the entity where you can enter a subdomain for it.

• User: e.g. "Mary" and all of her content at http://mary.example.com
• Taxonomy: e.g. "Seattle" and all content tagged with it at http://seattle.example.com
• Organic Group: e.g. "MyGroup" and all of its content at http://mygroup.example.com
• Content type: e.g. "News" content type and all of its nodes at http://news.example.com

Clean Pagination is a very simple module that allows you to enable clean URL pagination for specified pages. The way Drupal typically works, if you had a view with the URL 'my-view', subsequent pages would normally use a query to pass the page number, as in 'my-view?page=2'. When Clean Pagination is being used for a page, it will create a url like 'my-view/2'.

Currently, the module has just two settings: 1) Set the pages where you want clean pagination enabled, and 2) Enable search-engine-friendly pagination hyperlinks.

Path blacklist is a modest module with a very specific aim. Suppose you have paths in your domain that are handled further upstream (by Apache, IIS, etc.) and not by drupal, e.g., http://example.com/staff or http://example.com/intranet. You obviously don’t want your web editor mistakenly using these paths and, thus, creating nodes that will never be viewed.