Possibility to use different tree url for different level

I think you have explained the module in one sentence!

Can I try to explain your request in my own words?

You would like the URL itself (NOT an alias) to be cutomised?

So

 /ttm/[menu-name]/[term/%][node/%] 

would become something like,

 /[continent]/[menu-name]/[term/%][node/%] 

hokay!

1) If you want to make nice URLs without aliases, that's great! Because I get really good people on my queue, so nobody has mentioned it yet, but aliases are CONCEPTUALLY a problem with extended URLs and Taxonomy.

2) It's trickier than you might think. The /ttm/ is there to save this module from crazy people calling their vocabulary 'category', or even worse, somebody who is new to all of this using the word 'term'! Imagine the caos!

3) The coding is fairly easy (though extensive). You can't just slot in another bit of text, though. Each time you want to change a root like that, the module has to generate another menu item and push it into poor old Drupal.

I think we must have a unique name at the root. I am considering how to change this in admin.

Here's good. Due to the way this module positively builds a menu (as opposed to deriving it), naming by menu is really easy. In fact, if you use the extended URL option I've added, the menu name sort of works like this.

I know how nice it would be to have a URL,

asia/far-east/island-archipelago/indonesia/djakarta/accommodation

but it's asking for disaster round multiple hierarchy menus and user input. Treemenu V4 got really close to this, but the result was unacceptable for alias users.

Summary,

Changing the URL root: medium level priority for consideration.

Levels: already part of long term plans for the amazing, they said it couldn't be done, 'we follow while others lead', very good, sci-fi URL options future.

Right, I've thought about this. I need to loop through the unconsidered alias and Pathauto integration, and make some design decisions. So postponed. But some similar functionality is on the wish list for this module.

Ah - that is your wish?

While I have postponed this issue, for technical and time reasons, Treemenu can template by Taxonomy. You must be prepared to use a small amount of code in a preprocessor function. Also, you will have to construct your own page templates, I think. In return, you can often target whole menus, taxonomy terms (not just single nodes), and whole term descendant branches (which is quite spectacular, if confusing).

You need to look at the Help page 'code examples to help in styling Treemenus'. It should be more clearly organised, but time... time...

If you try this method, please post back, I'd be very keen to know how you get on.

Constructing an API for ctools/delegator sounds interesting - but I'll have to postpone that too - sorry, but that would be a long term priority (crikey, WHEN will someone help me out with this module?).

Yes, heirachy with templating would be fabulous, which is why I supplied all the code!

I work with a small video group called creakDV - and I use our site as a live testbed sometimes. Niether myself nor my friends have had a chance to update the site, so its a mess, but you can clearly see templating by Taxonomy

www.creakdv.co.uk

Rob

Also,

If you don't want to use templates/preprocessors, through developers such as yourself I'm gaining a good idea why.

As it happens, V4 of this module did as you asked. But the long URLs scared alias users (and the experimentatl nature was a bit broken too). See the module's internal help on the Ambiguous URL issue. Using the URL itself is not good. It makes a potential disaster where there are menus with user input. A URL needs something unique

But that doesn't mean - hey it can't be done. This feature is a long held wish of mine.

The plan is to see if I can coax the URL system into letting me work the menus, then optionally tag it with the taxonomy path for users like you and me. That way we get descendant term handling, of a kind, but good enough for most folks. It's a longish job, though, the titling, access and loading need to be confirmed working, and the re-written background fucntions asserted.

Rob.

In my head, yes! Pathauto integration and/or an addon module with the template code (thus providing a plugin solution) would do the trick, once I've cleared the URL issues (which were progressing rapidly, ideas were already in place in dev).

Practically, no. I can't even maintain Treemenu at the moment. So we are looking at six months, and a DRUPAL V7 edition as a timeline. Ouch! but that's the truth.

Rob