Don't know if it's a bug or just a not-allowed use case (limitation of the module).
Steps to reproduce:
1) Create a view with path a/b/c/d
2) Create a node with path alias a/b (let's say it's node/123)
3) Create a menu item pointing to your view (a/b/c/d)
4) the menu item will be wrongly stored as node/123/c/d
This can be quite annoying if you have a complex path structure with mixed nodes / views / panels pages working at any level of the path
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | node.PNG | 26.87 KB | marcoscano |
| #2 | view.PNG | 30.63 KB | marcoscano |
| #2 | menu_link_bug.PNG | 26.39 KB | marcoscano |
Comments
Comment #1
rdeboerHi marcoscano,
Interesting... thank you for your report.
As a workaround, do you really have to create a View named node/123/c/d ?
Rik
Comment #2
marcoscanoNo, in fact the view has path a/b/c/d, the path node/123/c/d is the result of the bug :)
I just tested on a clean install in simplytest.me, and aparently it doesn't happen in all situations. For example with node path: "a" and view path "a/b" it doesn't happen. But with node path "a/b" and view path "a/b/c/d?title=e" the bug reproduces.
Attached some screenshots of the problem
Comment #3
rdeboerOk, yes I'm with you now.
But creating a View that shares URL parents with the alias of another node, is asking for trouble, don't you think?
Rik
Comment #4
Leeteq commented#3: that's the question indeed; is it possible for this module to handle such cases, or should this be documented as a limitation of this module?
It would be _very_ useful if this module could handle such cases.
Comment #5
rdeboerListed as a limitation in README (7.x-1.x-dev and upcoming 7.x-1.2 release).
Patches welcome, but don't have the bandwidth myself right now. Sorry.
Rik