Problem/Motivation

Node sub-paths have no page manager context and make layouts a bit difficult. Simply, node/%node/%some_path pages that do not display in an admin theme, have no layout since they are not technically node/%node and Page Manager doesn’t kick in.

Clearly this may be a specific use case, but I do run into it regularly when building with Panels Everywhere. I prefer to not place page title and tabs in the Site Template, but rather place those items on Node, Term, or other page layouts. I first ran into this using Webform, but as we create other custom pages at node/%node/%some_path, it also occurs. I’ll describe it with Webform since it is a commonly used module.

How to recreate the situation using Webform as an example

  1. Enable Panels Everywhere, Webform, and all dependencies.
  2. In Appearance settings, disable “Use the administration theme when editing or creating content”
  3. Use a Panels Everywhere theme that does not place anything in the page.tpl.php such as Versatile
  4. Use a Site Template variant that only places Page Header and Page Content panes
  5. Enable the Node template and add Page Title, Page Tabs, and Node content panes to the display
  6. Create a Webform node and view it. Everything looks good so far.
  7. Click Webform tab. We no longer have access to page tabs because we are no longer using the Node view variant.

Proposed resolution

I’m wondering if it would make sense for pages at node/%node/%some_path to inherit the settings from node/%node or if there could be a default page for node/%node/%some_path where variants could be created based on the %some_path string?


There are certainly ways to work around this like introducing the Tabs pane or Page Navigation pane at the Site Template level with visibility settings to only show where needed, but I do find that we run into this often enough that there could be a generic solution.

Comments

jason.bell created an issue. See original summary.

DamienMcKenna’s picture

Category: Support request » Feature request

I think this might be a "works by design" because Drupal doesn't automatically inherit functionality from "parent" menu paths, it has to be specifically indicated.. I'll try to look into this.

jason.bell’s picture

Thanks for having a look. I finally found some related issues https://www.drupal.org/node/1188590 and https://www.drupal.org/node/1409842 that address the same idea of Page Manager tasks to handle add-ons that build pages at node/%node/some-sub-path. Page Manager Existing Pages does not seem to provide any help with this issue either.

In the meantime we will use custom task handlers as needed.