Hey guys, my issue is that panels is taking over the entire url tree even though its just supposed to be a parent. For example:

I have an article at url test.com/blah/blah2
Then I create a panel page at url test.com/blah

test.com/blah/blah2 is no longer available due to the panel page taking over.

Any advice would be greatly appreciated. If the bugfix is too time-consuming, please let me know if there is a way to programmatically display an existing panel page instead of creating a new one at a specific url. This way, I can alternatively fix it by just calling the panel page on test.com/blah

Comments

merlinofchaos’s picture

merlinofchaos commented
Priority: Critical » Normal
Status: Active » Closed (works as designed)

The way Drupal takes over menu items like that is not a bug. This is the standard Drupal behavior with menus.

Example: Visit node/1 and then visit node/1/foo and then visit node/1/foo/bar/baz.

You can fix this on a per panel basis by adding an optional context and then using access rules to ensure that context does not exist.

For example, if your path is 'foo', set your path to 'foo/!bar'. On the arguments page set bar to a string context. On the access rules page select the context exists rule and set it to NOT.

This is already in the queue in a couple of places.

Now, if you have a more specific menu item: blah/blah2 then blah should *not* take it over. However, that's core Drupal menu behavior. All I can suggest is that you make absolutely sure blah/blah2 is actually correct and what you entered. You don't normally have nodes at those paths, though you can ahve aliases. Aliases are checked long before Panels would even be in the picture.

Finally: This is all Page Manager, not Panels. :)