Path Management

User Case

The user has searched or filtered on a Views generated page,
clicked on one of the found results, and navigated through to the
page for that result.

After reading the info on the result page, how does the site lead
the user back to the page listing all the other found results?

This module provides a link back to the Views listing page,
which preserves the filters the user applied.

Page Manager (Panels) support for Profile2.

This module has maintenance status "Seeking co-maintainer(s)" because I don't really know how to fix the open bugs because of a lack of knowledge in ctools/page manager. So feel free to submit patches and/or apply for maintainer-ship!

With this module you can take over Profile2 paths with Page Manager.
Now it is possible to theme your Profile2 edit and view pages with Panels.

Provides context conditions and reactions on various CiviCRM pages.

Conditions:

• Contact type or Contact sub-type

Reactions:

Makes path/link elements autocompletable:

* Link field
* Menu item
* Redirect
* URL alias

These modules do **almost** the same, but too much or too little:

* https://www.drupal.org/project/mpac
* https://www.drupal.org/project/advanced_link
* https://www.drupal.org/sandbox/jlyon/2168455

Provides a blank <front> page (Landing/Home page) — that is not a node. As often, someone sets up a site using a content-type node with no actual Body content; as the frontpage. Then, at some future point a miseducated content editor un-publishes or deletes that node causing the site to break..

Interroedit lets you simply append "?edit" to a node alias when you wish to be redirected to the node's edit page.

For example, if node/123 has an alias of my/page, then your browser's address bar might contain "example.com/my/page". By editing your address bar to "example.com/my/page?edit" and hitting enter, you will be redirected to "example.com/node/123/edit".

This could be useful if your template does not render the edit tab.

Description

Have you ever wondered how to navigate through pages associated with various enabled modules? This module provides a solution for that. When we enable a module, often times we would like to see what links are associated with it. In this module, you will also be able to click on those links. As shown in the image of this module, you will notice that each module is represented by default as a fieldset and each of the links for the modules is grouped inside the module.

Dedupe Content, find and check the duplicated content allowing you to remove base on different fields.

Drupal is quite talkative in terms of showing off it's content. Often it makes content accessible which we actually don't want to show. That happens for instance very easily, if you're using nodes as content containers only - never really wanting to show the actual node pages of these containers.

Thanks to taxonomy node and similiar listings + some SEO javascript "callling home" often these unstyled content containers land on public search indexes as soon as an Administrator has an accidental look at these listing or node pages.

TLDR; A module to automatically update all path aliases of entities which reference separate entities whose path alias has just changed.

So you've set up your site to use clean URLs using Pathauto, and you have some logical structure to your paths - Great!

But you'll eventually run into a problem if you're intending to use Entity/Term reference fields with your content types (although it may not be so apparent).