D6 port - create secondary tabs for context switching

If somewhere in that discussion thread, someone indicated that it was possible to have multiple panel_pages per path, then they were in error. It is not, nor has it ever been possible for multiple panel_pages to reside on the same path. For D5, it will never be possible.

For D6, however, it will eventually be possible; the changes in the menu system allow us to be _much_ smarter about path collisions. It'll require me to abstract out into a separate API the system that I wrote for panels_page, which won't happen for at least a few weeks. This change will not add any new functionality from the panels_page perspective (that is, it won't permit any display switching that isn't already possible through the existing args system), but it will make it less weighty in the UI/conceptually to have a whole bunch of different displays for different node types. Chances are that this is what you're actually after - in which case you just need to check the "Use Own Display" checkboxes for each content type that needs its own unique configuration/appearance.

The goal of the node id arg modal config form, as it pertains to the non-title overriding stuff, is to allow you to have different displays per node types, as well as indicate that certain node types should not be rendered using the panels engine at all - i.e., it should fall back to the normal rendering process, node_view() in the case of a node/% path.

If what you are trying to do is add one panels page as a tab to another panels page, then you have to make sure that the parent path and the child path are initially the same, with an addition on the child path.

For example:

node/%

and

node/%/help

should work.

Ahh, sorry. No, because this deals with a subset of the menu system stuff that I've yet to get fully worked out. Sorry, I know it's a pretty debilitating problem, but I have to take these things in a conceptually sensible order (or I'll do them ALL half as well and in three times the overall amount of time).

But I'll switch this issue over and consider it the one for tracking progress on that particular need.

No. As I originally said, paths per type are not currently possible, will never be possible in D5, and will only be possible in D6 after a fairly hefty menu system abstraction & rewrite that I still need to do.

The problem has nothing to do with the underlying architecture being absent for handling context switching. It's just that the UI doesn't present you with tabs to easily navigate. If you know how to manually enter the URLs, though, it oughtta work...

Subscribing.

subscribe

could you give a clue about what the urls would be?

I've also tried to figure out the urls. I used a sandbox version of D5, set up the context, copied the url from the tab and tried to edit mine accordingly... Never worked once. If someone can confirm the URL method works, I'd be happy to make myself a little box with the links for myself to use in the meantime.

Between this and no user overrides, still too feature lacking for proper site development. Currently all nodes need the same layout, no user overrides, and limited mini-panel names, makes this usable for frontpage and maybe some other non-moving targets. Still my favorite module, but if I can't atleast layout my node types I, like many others may have to find an alternative. This is when I wish I could code instead of design. As I don't think anything else really compares.

The URL method probably does not work yet.

If there is anything that one can do to help move this along. I would love to help.

I am a php developer that has been working in drupal for about a year. and would love to help anyway I can.

Erik Summerfield
erik.summerfield at casefoundation.org

Dupe, and now fixed.