Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Are custom menu paths supported in the D7 version of the module? I tried the documentation, but I still see only the "Default" option. Is there something that I'm missing to make custom paths happen, or should I be more patient for a future release of Taxonomy Menu?
Thanks in advance for the advice.
Comment | File | Size | Author |
---|---|---|---|
#79 | taxonomy_menu-1035446-79-custom-paths.patch | 12.14 KB | hles |
#78 | taxonomy_menu-1035446-78-custom-paths.patch | 13.79 KB | hles |
#72 | taxonomy_menu-1035446-72-custom-paths.patch | 14 KB | hles |
#69 | taxonomy_menu-1035446-69-path_custom.patch | 8.99 KB | hles |
#68 | taxonomy_menu_1035446-68-path_custom.patch | 8 KB | hles |
Comments
Comment #1
dstolNope, you're not missing anything. It's being worked on, although patches are always welcome!
Comment #2
wheatpenny CreditAttribution: wheatpenny commentedThank you for your note. I hope that once I "get" Drupal that I'll be able to contribute. As is, this module is still solving 2/3rds of my navigation. Thanks!
Comment #3
essbee CreditAttribution: essbee commentedSubscribe
Comment #4
simon_s CreditAttribution: simon_s commentedsubscribe
Comment #5
WilliamV CreditAttribution: WilliamV commentedAre there any updates on this issue?
Comment #6
andypostMaybe this is related #975688: D7 Port of Taxonomy Redirect
Comment #7
Nick Robillard CreditAttribution: Nick Robillard commentedSubscribing.
Comment #8
xandeadx CreditAttribution: xandeadx commentedSubscribing.
Comment #9
Aracon CreditAttribution: Aracon commentedI ported 6.x-2.9 path_custom do 7.x-1.1. There was only one change in path_custom, in taxonomy_menu_path_custom.module, lines 65-69. It seems to be working.
The module also needs to apply the fixes to taxonomy_menu.database.inc from my another issue: http://drupal.org/node/1175470
Comment #10
ryanoreilly CreditAttribution: ryanoreilly commented@ #9 When I change the menu path type from "Default" to "Custom path" all my menu items disappear, but reappear when I change the path back to "Default."
Comment #11
Aracon CreditAttribution: Aracon commentedI'm sorry, I have no time at now to fixing this module, the aim was just to make it working in my project. Try to create a new menu with "Custom path" or to check the box "Update menus on save" before saving changes.
Comment #12
westbywest CreditAttribution: westbywest commentedI believe I was able to get taxonomy_menu_path_custom.zip working, i.e. menu items populated. But I had to set the variable for the custom path via drush; no options appeared for setting this field in the taxonomy vocab edit form.
E.g.
drush -u admin vset taxonomy_menu_taxonomy_menu_path_custom_base_path_2 custom_path
Comment #13
garethhallnz CreditAttribution: garethhallnz commentedI have spent hours looking into this problem and perhaps I am just missing something? The problem is registering a new path with arg(1) won't work?
So in the callback function for hook_taxonomy_menu_path()
$path = url('session-location/' . $tid); // WILL NOT WORK
$path = url('session-location/view/' . $tid); WORKS
This code works for me
Comment #14
dstolCould you guys please create a patch here? http://drupal.org/patch/create
Comment #15
marcoscanosubscribe
Comment #16
fotonarya CreditAttribution: fotonarya commentedAny update ?
Comment #17
Quarantine CreditAttribution: Quarantine commentedSubscribing - would appreciate it if someone could create a patch for this!
Comment #18
healycn CreditAttribution: healycn commentedsubscribe
Comment #19
ZuluWarrior CreditAttribution: ZuluWarrior commentedDefinatally Sub
Comment #20
ZuluWarrior CreditAttribution: ZuluWarrior commentedOk Guys,
Looked into this and I have a fail/win situation!
Win = I have worked out what it takes to get the solution in #9 to work under Drupal 7! details below!
Fail = I'm developing on a Windows machine, to a tight deadline so I have no time to delve into Putty, Git and making a patch file for this :( Perhaps later (it's on my Drupal nice to do list!), Sorry, anyway, instructions for zip in #9...
To Get Custom Path working:
Note: I am using Drupal 7.8, and Taxonomy Menu 7.x-1.2
(The one posted in #9 is fine but uses taxonomy_get_term() which is not in Drupal 7, so I changed that!)
(as per the structure of v6.x)
//$form['taxonomy_menu']['options'] = _taxonomy_menu_create_options($form['vid']['#value']);
Un-comment this line of code and save the file.
(This line is responsible for loading the extra form elements as highlighted in #10->#12
Hope this helps someone, I will try and create a patch when I can, otherwise is someone on Linux wants to do that for me, I'd be much obliged, as would the community!
Comment #21
amogiz CreditAttribution: amogiz commentedIt really did not work for me …
I lost everything, had to uninstall taxonomy menu to get it work again …
THe error I got is : Notice : Undefined property: stdClass::$language dans _taxonomy_menu_create_item() …
If I don't use the options but only the "module" menu path, noting works.
I have to stop my website if no solution …and do it again on D6 … So I am really expecting a solution :)
Comment #22
Nick Robillard CreditAttribution: Nick Robillard commentedFyi, for those waiting on this for D6, the Views Hacks sub-module Taxonomy Summary has been improved upon and accomplishes this almost exactly. #1199600: Custom url and record count options (Make sure to use the dev version of Views Hacks)
Comment #23
amogiz CreditAttribution: amogiz commentedOh please, could it be possible the get the options with the custom path working ?
As i said in another post about this taxonomy menu option, in my case, i May Have ti do my website again in D6 and it's really a disaster …
Thanx
Comment #24
ZuluWarrior CreditAttribution: ZuluWarrior commentedamogiz,
Did you try a vanilla install of Drupal 7.8, Taxonomy Menu 7.x-1.2 and the above patch?
I have the feeling something is out of place as in the example I supply above I don't have a 'module' option, I only have "Default" and "Custom path" (following the patch). This makes me think you have another module in there at least?
I don't profess to being an oracle on Taxonomy Menu, but I did learn a bit with the patchwork I did a few weeks ago, so if you wish I'm happy to help where I can! Drop me a message with any detail you have (If your on any IM clients let me know which one and when your online too!), modules, version numbers ect, and I'll put some time aside one evening this week (I am in UK) to see if we can't get something working for you.
(I too am in limbo and considering a D6 rebuild (however my issues are with Media module), so I feel your pain. But Taxo-Menu shouldn't be a complete show stopper, I will help if I can!)
Comment #25
flexman CreditAttribution: flexman commentedFirst of all, thanks for the work on this Zulu... I seem to be having the same issue as amogiz. I install the patch module, and un-comment the specified line of code and the menu to be displayed is removed completely. When I edit the taxonomy vocabulary, I see the "Custom path" option, but making any changes does nothing. To get the original default menu back, I need to uninstall the Taxonomy Menu module. Has anyone been able to successfully get this working?
Comment #26
johnvHere's a proper patch for #20 (including a Coder review).
It contains 2 files, since the change in module-file may be already in your system for other issues.
My remarks sofar:
- the taxonomy menu path for the term page is created correctly; (OK)
- the option 'use term name' does not work: the URL-path is still base-path/tid (TODO)
- I can reset 'menu path type' from 'Custom path' to 'Default' and Save. After that my old situation is restored, (using paths created with Pathauto). (OK)
- My existing menu block for the taxonomy menu had been vanished with 'Path custom'; perhaps needs some redefinition;
- I did not create a view yet, while settings page says 'You need to have a view..'
- I do not use multilanguage
BTW: Does this mini-module have advantages above Pathauto ? , otherthen being a dedicated alternative?
I set this issue to Needs Review, hoping for a testbot review.
@amogiz, please reset to Needs Work if your issue hasn't been resolved yet.
Comment #28
johnvComment #29
johnv-p1, -p0, haven't figured it out yet.. Anyone?
Comment #30
ZuluWarrior CreditAttribution: ZuluWarrior commentedHi johnv,
Many thanks for working on this, I shall give it a whirl later next week and post back. Am I right in thinking that your patch also tackles (or at least has ToDo) the vocabulary as menu item problem (which is a seperate issue somewhere else in this issue queue?
regarding : "BTW: Does this mini-module have advantages above Pathauto ? , otherthen being a dedicated alternative?"
My use case requires both pathauto and taxonomy_menu + custom path. Pathauto sets the url_alias's for the taxonomy terms, but does not expose taxonomies in a menu, in my case this module fulfills that use case of exposing the taxonomy (and paths set with pathauto) to the menu, without admin intervention (using the update menu on vocabulary edit option).
Comment #31
johnvHi ZuluWarrior,
no, my patch is a straight copy of your's. I have no plans in extending it.
regarding pathauto vx path_custom: OK, I see now, the building of a menu and the creation term path are 2 separate things. You could have 2 menu's pointing to the same page.
Comment #32
johnvHere's a better version of #26-#28.
It contains 2 files, since the change in module-file may be already in your system for other issues.
- didn't test translations of term names
- didn't test 'display_descendants' since that option hasn't been ported yet to D7.
Comment #33
rofsky CreditAttribution: rofsky commented#32: taxonomy_menu_1035446_32_module.patch queued for re-testing.
Comment #34
dstolI made a couple of commits this evening that probably affect the module.patch in #32.
Comment #35
brianfisher CreditAttribution: brianfisher commentedfix #32 to work with latest 1.x
sorry about the filename, but this patch creates taxonomy_menu_path_custom.info and taxonomy_menu_path_custom.module
Comment #36
brianfisher CreditAttribution: brianfisher commentedfix warning in #35
Comment #37
dstolThis needs to have tests associated with it before I commit it. http://drupal.org/simpletest
Comment #38
andypostAlso code should be checked for coding standards, currently there's some trailing whitespace and code comments ... try to check this with dgo.to/coder module
is not used after git migration
Should be Implements hook_
the same
needs space after // and coment should not be wider 80 chars
trailing whitespace
Comment #39
1800collect CreditAttribution: 1800collect commentedSubscribing.
P.S. Thanks everyone who is working on this! If I could read the patch code I'd try it out myself. One step at a time and I may be savvy enough for it.
Comment #40
carn1x CreditAttribution: carn1x commentedCan anybody comment whether these patches are actually working? I'm a little confused by the fact there are 2 patches almost identical, I assume only one is required?
Either way, I've tried to use each deploying manually alongside 7x-1.2.
Both provide a "Custom Path" option on the Vocabulary edit page, but beyond that, they fail to provide any additional form items to customize the path, which means I guess they don't work.
I'll try with 7.x-dev as well.
Comment #41
carn1x CreditAttribution: carn1x commentedOk, tried now with 7.x-1.x-dev, and using Custom Path option simply causes the menu to disappear. Switching back to Default makes the menu appear again.
Comment #42
carn1x CreditAttribution: carn1x commentedAhh right seems I wasn't reading the instructions for base path and was entering 'path/%' instead of just 'path' :) All working fine now.
Comment #43
fonant CreditAttribution: fonant commentedThis works for me, enabling custom menu paths, by doing:
Comment #44
Ashlar CreditAttribution: Ashlar commentedI've been working on the same function as is modified in the patch at #36. The purpose of my exploration is to change the path of individual links depending upon the value of field attached to the taxonomy term. So far every attempt has generated the same path for all terms. I find this confusing. My read of the function is that it is assigning the path to each individual link item, but the results don't work that way. Can anyone shed a little light on this. Should I be testing the tid and modifying the path at some other location in the module. I tried it in _taxonomy_menu_save interpreting the code as saving an individual item in the menu, but ended up with all links with the same ending. Am I misinterpreting how to change individual paths?
This code shows the modification I was attempting. Thanks for any comments!!
Comment #45
liats75 CreditAttribution: liats75 commentedThe patch from #36 works for me also. thanks!
Comment #46
ZuluWarrior CreditAttribution: ZuluWarrior commentedHi all,
Thanks to johnv and tbfisher for rolling those patch files up for us.
Sorry but I think there is a critical line missing from it though. My origional suggestion mentions in #20 mentions the need to uncomment a line in taxonomy_menu.module, so that the 'custom path' options are displayed, allowing the user to set the costom path and other options such as include parent and include all ect.
Basically all thats needed is line 73 of taxonomy_menu.module (7.x-1.2) needs 'uncommenting'. Change :
to
and the form comes back. Agree there probably needs to be a test set before commiting, but can't we copy the custom path tests for 6.x? After all its almost the same module!
Anyway, thanks again guys, after doing the above I find taxonomy_menu_custom_path working well with my latest 7.12 site.
Comment #47
Jim Ruby CreditAttribution: Jim Ruby commentedsubscribing, thanks to all who is working on this.
Comment #48
jmann8888 CreditAttribution: jmann8888 commentedHi, Im not quite sure how to apply a patch, but i do know that what is on this page is what i want of my drupal site, if someone could pump out this module with all these patches applied, that would be VERY MUCH appreciated.
Thank you in advance :)
Comment #49
westbywest CreditAttribution: westbywest commented@jmann8888 To patch the module at the command line in an OSX/Linux/*nix enivornment, I downloaded the patch attached to comment #36 to the taxonomy_menu module's directory and then ran the patch command:
More info:
https://drupal.org/node/60108
Comment #50
nirad CreditAttribution: nirad commentedI couldn't get this to patch (#36) to work for me. Could it be related to the fact that I have the Entity Path module installed? It doesn't seem like this module checks for the actual path, so I don't see how that would effect it. OTOH, it could be worth looking at that module as an example of how this module could work.
Comment #51
MrPaulDriver CreditAttribution: MrPaulDriver commentedAlso struggling.
My first attempt at patching and thought I'd done everything correctly but still only seeing the default path.
As with #48 it would be most helpful if someone with a bigger brain than myself could roll this out to dev.
Comment #52
MattBrigade CreditAttribution: MattBrigade commentedI managed to come up with a workaround to the custom path issue while this patch gets committed. I created a simple custom module called "taxonomy_menu_mods". Inside taxonomy_menu_mods.module I called hook_menu_link_alter() to alter menu item paths being saved by Taxonomy menu.
Here's an example of how I used hook_menu_link_alter(). This example was used for the vocabulary I named "Portfolio" (with a VID of 2). I needed to changed the path to go to "project-portfolio/%term-name". I hope this example makes sense and you're able to modify it for your own use case. I can further elaborate if anyone would like me to.
Comment #53
stuhannaford CreditAttribution: stuhannaford commentedCan confirm dev + #36 work. Thanks for everyones help on this one.
Tried with 1.2 without any joy and had to manually create the path_custom.info file just so that the custom option was displayed. Even then there weren't any options to actually create a custom path.
I had a slightly different requirement to the argument based option where I wanted the menu items to link through to an exposed filter in views, i.e. 'base path/store?tid=%'. As the module automatically added the trailing slash, I manually removed '/' from lines 70 and 73 (e.g. $path = $base_path . '/' . $end;) in path_custom.module which allowed me to do this. Is it worth removing that slash from the patch so that it gives people the option to add it or not as opposed to hacking away at the patch?
All up and running at www.prettyformal.co.uk if anyone wants to see
Comment #54
rc_100 CreditAttribution: rc_100 commentedI downloaded the dev version and applied patch from #36, however I got an error after saving a node with a taxonomy term attached ($tids variable on line 92 of taxonomy_menu_path_custom.module). Seems to work fine after I change that line from this:
$tids = ($tids) ? $tids : array($tid);
to this:
$tids = (isset($tids)) ? $tids : array($tid);
I assume that's because I only had one term in my vocabulary!
Comment #55
MrPaulDriver CreditAttribution: MrPaulDriver commentedDid a solution to this issue get committed to latest dev of 2012-Jul-19?
Comment #56
Barrett CreditAttribution: Barrett commentedNo, an explicit fix has not been committed. The latest patch still needs work, as discussed in comments 37 and 38.
Comment #57
Anonymous (not verified) CreditAttribution: Anonymous commentedThanks @mattbrigade #52 worked well for me as a temporary workaround until this patch gets committed. A bit off topic, but a couple of tips that would have just saved me an hour: 1) hook_menu_link_alter() only gets called when you save a menu, not when you render one on a page, and 2) you can't add URL arguments in $item['link_path'], you have to add them separately like this:
Comment #58
melvix CreditAttribution: melvix commented#52 worked for me, too.
To expand on what jackocnr said in #57:
After you add your version of hook_menu_link_alter(), you will probably need to visit the edit screen for vocabulary you're using (admin/structure/taxonomy/vocabulary_XX/edit), check "Select to rebuild the menu on submit" and re-save.
Comment #59
Anonymous (not verified) CreditAttribution: Anonymous commented#36 + #54 worked for me with Taxonomy menu 1.4!
But then I couldn't find a way to make it work with "Taxonomy Menu Trails" module... Anyway thank you guys for your work!
Comment #60
clashar CreditAttribution: clashar commented#36 works well for me with Taxonomy menu 1.4.
Comment #61
johnvAfter updating to Taxonomy menu 1.4, and implementing #36, I got the following warning when editing a node with a relevant Vocabulary:
Fatal error: Call to undefined function taxonomy_menu_path_custom_create_path() in .../taxonomy_menu/taxonomy_menu.module on line 724
I fixed it by going to the vocabulary-edit page and save the page.
Comment #62
pointdexter02 CreditAttribution: pointdexter02 commentedFor those of you that got it working with 1.4, what did you need to do?
I did it manually by creating the 2 files in the taxonomy menu folder and then looked at the main module code, but that line is not commented out. I'm not getting any extra options in my settings.
Am I missing something?
Comment #63
kmare CreditAttribution: kmare commentedHello,
I just wanted to report that patch #36 worked like a charm for me without any problems. It would be awesome if it could be applied on a released version.
Thank you!
@pointdexter02: just apply the patch, no need to mess with any line or so. Just set your custom path and you should be good to go. Not sure if it's really needed, but just to be sure clear your cache.
Comment #64
hles CreditAttribution: hles commentedPatch needs to be ported to 7.x-2.x and provide tests like dstol said previously.
Comment #65
monstordh CreditAttribution: monstordh commentedThe patch didn't work for me. Custom menu paths for my taxonomy is the primary reason I use this module. Now, since (reluctantly and regrettably) migrating to D7 I have completely lost a central component in my functionality. Are there any plans on getting this fixed soon?
Comment #66
hles CreditAttribution: hles commentedWhat needs to be done:
- Port the patch to 7.x-2.x, there are not a lot of modifications to do really (http://drupal.org/node/1035446#comment-5321920)
- Fix the Drupal coding standard issues (http://drupal.org/node/1035446#comment-5324210)
- Add some tests
Any help would be appreciated on this one as we are already working on making stable the 2.x version of Taxonomy Menu.
Comment #67
brianfisher CreditAttribution: brianfisher commentedported to 2.x branch
Comment #68
hles CreditAttribution: hles commentedThank you tbfisher ! I created a new patch taking advantage of the hook introduced in commit 5f92314. Tests have not been reviewed at all.
Comment #69
hles CreditAttribution: hles commented- Added validation so it can detect whether a path is registered.
- Added states to the "custom path options" fieldset in order to make it disappear when custom path is not selected.
- Fixed a few things in tests but they are still not passing for now.
- Removed the "use term name" option for now, but will add it again later.
- Fixed typos, added more comments.
It would probably work fine enough but this is still work in progress.
Comment #70
pointdexter02 CreditAttribution: pointdexter02 commentedLooks like some may have had the same issue I am and I'm wondering if it's been figured out. I got the patch working and when I switch to custom paths to get it to use catalog pages as the link url's, all of the catalog items disappear from my menu. Then when I put it back to default, they come back. The thing is, it's not just on the page display of the menu. If I physically go in and look at the menu list items, all of the catalog items are gone. The only thing that displays are the items I added to that menu, not associated with the taxonomy terms. Any thoughts? Thanks!
Comment #71
hles CreditAttribution: hles commentedThanks for testing the patch. Your problem is probably due to the fact that your custom path is not available in Drupal. For example, if your base path is 'catalog' and you don't use the depth setting, you must have the path catalog/% registered in Drupal (by creating a page view for this path for example). With the depth setting, it would be catalog/%/%.
I have an newer version of this patch that will check that the paths exist before creating the taxonomy menu, during the form validation process. I'll post it later today probably.
Comment #72
hles CreditAttribution: hles commented- Fixed existing tests
- Added functional tests
- Added validation of custom paths so a taxonomy menu is not created if the custom path in the options is not yet registered
Comment #73
pointdexter02 CreditAttribution: pointdexter02 commentedAlright, I really appreciate the info hles. Now I have a new issue. So I got the taxonomy menu links to work properly in going to catalog pages. i.e. catalog/product, but when I click on the links, the page that's displayed is no longer the list of products, just a list of:
taxonomy 1
Term ID: 11
taxonomy 2
Term ID: 8
taxonomy 3
Term ID: 10
taxonomy4
Term ID: 9
taxonomy 5
Term ID: 15
Which doesn't change for any of the different pages in the list. It seems to have broken the standard catalog block as well. What do you suppose I did?
Comment #74
hles CreditAttribution: hles commentedCan you tell me which settings you have in taxonomy menu ? Base path and depth ? And also the exact path that is generated in your taxonomy menu links ? If all that is correct, then it's probably a problem within your view, but let's check taxomy menu first.
Thanks for testing btw !
Comment #75
hles CreditAttribution: hles commentedUnassigning from myself as I won't be able to work on this for a few days.
Comment #76
pointdexter02 CreditAttribution: pointdexter02 commentedThanks hles. It was, in fact, an issue with my view. Not sure how it got all screwed up, but it's good now. My only issue left to solve to make it perfect is that in the menu, when I click a product category, it doesn't expand the menu item. If I check box the expand all, everything's expanded and all links work perfectly, but that won't work for me in the long run. Any thoughts? Thanks again.
Comment #77
hles CreditAttribution: hles commentedI'm not exactly sure what behavior you expect, but it looks like your problem could be solved by Taxonomy Menu Trails.
That would be great to have some feedback from one more person so I can eventually close this issue, commit this code in the 7.x-2.x branch and release an alpha2 version with all the latest improvements.
Comment #78
hles CreditAttribution: hles commented- Moved helper module for paths registration to taxonomy menu 'tests' folder.
- Added missing new lines at the end of files.
Comment #79
hles CreditAttribution: hles commentedCommited helper module for paths registration in 7.x-2.x branch. Updated patch.
Comment #80
hles CreditAttribution: hles commentedRemoving tag.
Comment #81
brianfisher CreditAttribution: brianfisher commentedtested latest patch, looks great. Thanks hles!
Comment #82
pointdexter02 CreditAttribution: pointdexter02 commentedI am under the impression that the behavior I want is covered under menu trails as well, but I just can't seem to link the two up. If I leave the menu on default (taxonomy/term/tid) The active trails on the menu will expand sub-categories as I would expect, but when I switch over to a custom path (catalog/%), the active trail doesn't follow and only the top level will display in the menu when clicked. I've set the menu trails option to "ask taxonomy menu" for paths and tried everything else I can think of.
Comment #83
hles CreditAttribution: hles commented@tbfisher thanks for testing !
@pointdexter You should try posting an issue in Taxonomy Menu Trails issue queue and see what the maintainer has to say about it. I have no clue how that module works and maybe he could solve the problem or at least point you to a direction to follow.
Comment #84
pointdexter02 CreditAttribution: pointdexter02 commentedMuch appreciated. Will post if I figure out the solution.
Comment #85
hles CreditAttribution: hles commentedPatch #79 commited with some small modifications. Thanks to everybody for working on this !
Comment #87
wmad CreditAttribution: wmad commentedFor those who are looking for a solution for 7.x-1.x, check out http://drupal.org/node/1516146
The solution involves installing the taxonomy_display module: http://drupal.org/project/taxonomy_display
Comment #88
giupenni CreditAttribution: giupenni commentedI've installed 7.x-2.0-alpha2 but I can't set Base path for custom path.
Any path that I insert I have this message:
"The path catalog/% is not available in Drupal. This is required to use custom paths."
Comment #89
brunorios1 CreditAttribution: brunorios1 commented@giupenni,
install the dev
Comment #90
giupenni CreditAttribution: giupenni commentedIn dev version I can't enable taxonomy menu custom path, in admin/structure/taxonomy/catalog/edit I show only Taxonomy Menu module and not Taxonomy menu custom path.
Infact when I configure the module, in Menu path type I can select only Default.
Comment #91
brunorios1 CreditAttribution: brunorios1 commentedhave you enabled the module taxonomy menu custom path?
cleared the cache?
Comment #92
giupenni CreditAttribution: giupenni commentedYes.
I'm using Ubercart and I must make a menu for Catalog, I'm trying to use this solution http://drupal.org/node/919944#comment-3483120 but when I insert "Catalog" in Costum path I have this error:
"The path catalog/% is not available in Drupal. This is required to use custom paths."
The catalog path exists.
Comment #93
bortolotte CreditAttribution: bortolotte commentedFirst, thanks to all who are supporting this "Custom menu path" porting for D7.
I've tested 7.x-2.0-alpha2 version and it "seems" to work. i.e. the "Custom" option is now available.
However, I say "seems" to work, because I couldn't put it to run, once the 'Custom' option in "Menu path type" requires a '<base_path>/%' URL, whose wildcard ('%') does not allow Views to be added to Menus in "Views > Displays > Page Settings > Menu".
To make it clear, this is what I want to do in my site:
Maybe if Custom menu path used Token module support (e.g. <base_path>/[term:tid]), this problem would not happen when trying to add Content View to Main Menu, once no '%' would be used in Views page address.
Does it make sense to you guys? If so, could anybody implement this Token module support in Taxonomy Menu?
I'm a bit new to Drupal, so, please anyone clarify my thoughts in case I'm missing something.
Thank you very much!
Comment #94
DigitalFrontiersMediaI think your problem is that you need to make sure the Views Page display uses the same path (/%) and you ONLY enter into the "Custom Path Options since the '%' is filled in for you by tm_custom_paths.module as Term ID.