I am using this module to fix an issue I had with Page Manger where I created a custom page to show comments in a separate Menu tag, but the link was showing up as node/XX/comments, instead of friendly URL like the associated article. That worked, but then I noticed the Context module was set to show some other blocks on the Articles pages. Those worked as expected, but since the ailias for the comments was "articles/a-bunch_of-stuff/comments, I expected the context path "articles/* to work for both the articles menu tag and the comments menu tag, but they did not. I had to modify the context path to add "node/*/comments" for the blocks to show up on the comment page. I expected the modules alias to take care of that.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | node path works.png | 6.6 KB | JSCSJSCS |
| #5 | record alias does not work.png | 6.84 KB | JSCSJSCS |
| #5 | views path setting.png | 5.49 KB | JSCSJSCS |
| #3 | context_integration-1457348-3.patch | 1.19 KB | guillaumev |
| had_to_add_node.png | 14.55 KB | JSCSJSCS |
Comments
Comment #1
rdeboerThanks for your report James,
I think you want Extended Path Aliases to do more than it was intended for -- e.g. doing what could be considered other modules' jobs.
I may revisit this, but for now, I'd like to re-classify this as a feature request (and perhaps not even a feature request for Extend Path Aliases...).
Rik
Comment #2
JSCSJSCS commentedOkay. Thanks for taking a look at it.
Comment #3
guillaumev commentedAll you need to do in order to have path alias xt work with context is to set the module weight of path_alias_xt to -1 (and then clear your cache) in order to have path_alias_xt_init executed BEFORE context_init.
Here is a patch attached to this that will update path_alias_xt to work with context (and also other modules, such as menu_trail_by_path).
Comment #4
rdeboerThanks so much guillaumev!
Patch looks good.
Hope to apply soon.
Rik
Comment #5
JSCSJSCS commentedThis patch has been working great with the page manager alias issue I first reported. I have since used the path_alias_xt module to fix another issue I had with the Views page menu tab path. Since those paths have to be the real path prefix in order for the tab to show up on the node view, the path looked something like this "node/8384/premium_information", instead of "record/pathauto-title/premium_information"
I remembered this module and installed it. It fixed this problem as well! The browser displayed the new views path as the extended alias. Terrific!
I was using "node/*/premium_information" in the context path which was working, but wanted to be consistent as before:
So I tried changing the previous context path statement from "node/*/premium_information" to "record/pathauto-title/premium_information" and the blocks fell apart (did not show up as context layed out).
But then I remembered there was a patch.
I tried installing the patch from @guillaumev and it failed. I checked the module dates and determined I had installed the dev version and the patch must only work on the older recommended release, so I installed that and the patch applied successfully.
However, the new context path still does not work.
Is there a difference with the way page manager aliases and views path alias would interact with context module?
Comment #6
JSCSJSCS commentedStill using the patch from #3 and ran into another contrib module issue where I am using page manager to take over node/%node/premium
however, setting a context module path override to ~dealer/*/premium (the PM override path) did not work
I had to use the original path to override using ~node/%node/premium
Comment #7
rdeboerPatch from #3 applied to 7.x-1.x-dev (soon to be 7.x-1.1).
Thanks GuillaumeV.
So sorry for the delay. This module dropped off my radar for some time...
Rik