Multi page node_view
| Project: | Panels |
| Version: | 6.x-3.0 |
| Component: | Panel pages |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Hello
Thanks for the extremely useful module. I have successfully set up a node_view page to display a range of info related to one of my content types.
This is all working great on one page. However, I find that I need to create more pages to hold all the info I want related to each node.
In an ideal world I would do this through adding an argument to the url - eg content/my-node-title-name-here/argument-1 content/my-node-title-name-here/argument-2 etc and constructing new panel pages to hold the information (and a custom menu tab to link the pages together).
However, I realise that Drupal Url node aliases do not work this way - that they resolve the whole URL path without breaking up the elements - so are unable to take arguments. I have installed Sub path URL alias http://drupal.org/project/subpath_alias to try and fix this issue. With this installed have tried setting the path of new panel pages as node/%node/argument-1. However, this still generates a page not found when viewed from content/my-node-title-name-here/argument-1 and seems to have other unpredictable results.
Before I get too deep into this (which I appreciate may be an issue for this module rather than Panels), I wanted to check that there was not a more obvious way of doing what I want to achieve - effectively to have several pages, ideally with their own clean URL path that each can be customised to show different information related to a node.
Thanks very much for any help.
#1
There isn't, currently, a more obvious way to do this that I can think of. I have no experience with the subpath_alias module, either, though it sounds pretty useful for stuff like this.
Without actually seeing the system in action, I don't have a good answer for why you're getting a 404 on those pages, either. Perhaps the sub-aliases are not being set up properly?
#2
Thanks for the advice. It's possible that I've not set up sub aliases properly. I'll investigate and post here if I solve it.
It would be great if functionality of this sort could somehow be built into Panels in a future release.
#3
It is an interesting requirement, and I can imagine it being a fairly common one. There isn't really an easier way to do it right now, so I agree that that sort of subpath aliasing probably would be your best bet.
If such functionality ever were to be built-in, it would probably be in Page Manager. But I think I'd rather avoid touching the alias system at all; rather, I think a better solution would probably involve some kind of inheritance relationships between different panels. That's a big can of worms, though.