Path Management

Controls block visibility by URI Query Parameters. Drupal natively allows blocks to be placed on pages by using their paths, however, this module allows administrators to also display modules based on url query parameters.

• Supports both "All pages except those listed" and "Only the listed pages"
• Can be used in conjunction with page visibility
• Administrator can set both the query parameter and value - the module is just looking for an arg=value pair

Example uses:

lndex - language index

This tiny module allows site administrators to define own paths for language switch links.

Provides an option to rebuild the URL aliases of all pages in a book on the node edit form of the top page of the book.

What does this module do?

This Module adds an optional "BULK UPDATE" operation to the pathauto module.
Here: admin/config/search/path/update_bulk called "Taxonomy term paths for i18n"

Info

Currently only BULK UPDATING works. Patches welcome.

Token support

Uses basic token support from i18n and adds support for [term:i18n-parents:*] chained tokens.

Why?

You can generate taxonomy paths in the translated language so that the user gets the path in his language

Example:

Creates a nodetype for redirection nodes - i.e. nodes with a link to an internal or external resource that will be the destination for this node.

Usages:
For e.g. nodequeues with frontpage items where you want a "click-friendly" title, image or summary, but retain another title and other content on the actual node.

Or in order to share (links to) content between several sites, you can create a redirection node on one site that points to the content node on the other site.

Features:

The front page redirect module redirects visitors that arrive on the front page of your site to the page that is defined as the default front page.

Create separate pages for different view modes for a given content type.

8.x Branch:

• Requirements

  • Drupal 8.1+
  • Token
  • CTools

• Configuration

  On the configuration page you can add as many path patterns as you desire, path patterns are based on the regular entity url's/aliases.

  For instance, if you want to show the teaser at a specific URL.

This module implements the crossdomain.xml file on sites that require it. The module provides the ability to hook into the standard output for further customization.

This module keeps track of the URL path for each revision of a node.

Possible uses include URL rewriting in a front-end cache (using a database lookup) or tracking when a URL path was changed.

There is no real frond-end interface apart from a simple text field in Views, but there is an API and the path revisions are available in the node object.

This module is pathauto-aware.

This module allows you to put any relative path you'd like for a menu entry, even if the path doesn't exist on your site.

You might need this module for two reasons.

1) You either need to create menu items before the pages/paths are created. Helpful when you are building out new sites for which you haven't actually created the secondary pages yet, or if you want your menu to point to some path that will actually be redirected somewhere else (for which you've already set up a redirect).

This actually isn't why this module was created, but it will work for this.