Taxonomy_menu support for Token/Pathauto

Hi there,

No I ddin't get it working. And there doesn't seem to be a maintainer for this module either. :(

B/

As a temporary solution, you can probably manually create the menus for your site. That's what joomla does by default. As far as I know joomla doesn't have this functionality in it's default distribution. Maybe in it's extensions...?

I'm using this code in .htaccess to rewrite taxonomy_menu URLs as taxonomy/term/nn, which global-redirect then takes care of, by redirecting the user appropriately:

# Rewrite taxonomy menu urls. this would ideally be done in taxonomy menu module
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} /taxonomy_menu/.*$
RewriteRule ^.*/(.*)$ /index.php?q=taxonomy/term/$1 [L]

Above

# Rewrite current-style URLs of the form 'index.php?q=x'.
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

The taxonomy_menu/nn/n urls are still output to the source, but are always redirected once clicked on.

If you want the ideal solution, I suggest you have a go at peterx's solution here: http://drupal.org/node/41476#comment-181146 and here http://drupal.org/node/103539. Core menu is such that it is impossible for taxonomy to write menu tree-paths that are different to drupal paths using hook_menu. So peterx's solution is rather complicated and requires several core hacks.

@graphicsplus

I installed Global Redirect (latest dev version, not official release), Pathauto 5.x-1.1, DHTML Menus 5.x-0.7, and Taxonomy Menu 5.x-1.x-dev. Show the taxonomy menu block in admin/build/blocks, then check that the menu items in that block link to taxonomy_menu/[tid]/[tid]/[tid]. Where [tid] is an integer that is the tid of the term, or one of it's ancestor terms. Make sure clear URLs are enabled and working.

Now look for this code at the bottom of .htaccess:

# Various rewrite rules.
<IfModule mod_rewrite.c>
  RewriteEngine on

  # If your site can be accessed both with and without the prefix www. you
  # can use one of the following settings to force user to use only one option:
  #
  # If you want the site to be accessed WITH the www. only, adapt and
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
  # RewriteRule .* http://www.example.com/ [L,R=301]
  #
  # If you want the site to be accessed only WITHOUT the www. prefix, adapt
  # and uncomment the following:
  # RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
  # RewriteRule .* http://example.com/ [L,R=301]

  # Modify the RewriteBase if you are using Drupal in a subdirectory and
  # the rewrite rules are not working properly.
  #RewriteBase /drupal

  # Rewrite old-style URLs of the form &apos;node.php?id=x&apos;.
  #RewriteCond %{REQUEST_FILENAME} !-f
  #RewriteCond %{REQUEST_FILENAME} !-d
  #RewriteCond %{QUERY_STRING} ^id=([^&amp;]+)$
  #RewriteRule node.php index.php?q=node/view/%1 [L]

  # Rewrite old-style URLs of the form &apos;module.php?mod=x&apos;.
  #RewriteCond %{REQUEST_FILENAME} !-f
  #RewriteCond %{REQUEST_FILENAME} !-d
  #RewriteCond %{QUERY_STRING} ^mod=([^&amp;]+)$
  #RewriteRule module.php index.php?q=%1 [L]

  # Rewrite current-style URLs of the form &apos;index.php?q=x&apos;.
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
</IfModule>

Replace it with this:

# Various rewrite rules.
<IfModule mod_rewrite.c>
  RewriteEngine on

  # If your site can be accessed both with and without the prefix www. you
  # can use one of the following settings to force user to use only one option:
  #
  # If you want the site to be accessed WITH the www. only, adapt and
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
  # RewriteRule .* http://www.example.com/ [L,R=301]
  #
  # If you want the site to be accessed only WITHOUT the www. prefix, adapt
  # and uncomment the following:
  # RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
  # RewriteRule .* http://example.com/ [L,R=301]

  # Modify the RewriteBase if you are using Drupal in a subdirectory and
  # the rewrite rules are not working properly.
  #RewriteBase /drupal

  # Rewrite old-style URLs of the form &apos;node.php?id=x&apos;.
  #RewriteCond %{REQUEST_FILENAME} !-f
  #RewriteCond %{REQUEST_FILENAME} !-d
  #RewriteCond %{QUERY_STRING} ^id=([^&amp;]+)$
  #RewriteRule node.php index.php?q=node/view/%1 [L]

  # Rewrite old-style URLs of the form &apos;module.php?mod=x&apos;.
  #RewriteCond %{REQUEST_FILENAME} !-f
  #RewriteCond %{REQUEST_FILENAME} !-d
  #RewriteCond %{QUERY_STRING} ^mod=([^&amp;]+)$
  #RewriteRule module.php index.php?q=%1 [L]

  # Rewrite taxonomy menu urls.  this would ideally be done in taxonomy menu module
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} /taxonomy_menu/.*$
  RewriteRule ^.*/(.*)$ /index.php?q=taxonomy/term/$1 [L]

  # Rewrite current-style URLs of the form &apos;index.php?q=x&apos;.
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
</IfModule>

The bit that's different here is

  # Rewrite taxonomy menu urls.  this would ideally be done in taxonomy menu module
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} /taxonomy_menu/.*$
  RewriteRule ^.*/(.*)$ /index.php?q=taxonomy/term/$1 [L]

which is essentially the same as

  # Rewrite current-style URLs of the form 'index.php?q=x'.
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

just below it. Except that it has an extra condition, and it changes the path. I've commented it extensively below. These give a complex instruction to apache about how to handles an http request.

  RewriteCond %{REQUEST_FILENAME} !-f # If this path isn't a file on the filesystem (like files/images/photo.jpg),
  RewriteCond %{REQUEST_FILENAME} !-d # and this path isn't a directory on the filesystem (like files/images),
  RewriteCond %{REQUEST_URI} /taxonomy_menu/.*$ # and this path contains the string '/taxonomy_menu/' (including the slashes, e.g. '/taxonomy_menu/23/56/3') (should work okay without friendly urls if you remove the leading slash),
  RewriteRule ^.*/(.*)$ /index.php?q=taxonomy/term/$1 [L] # then don't look for a file that matches 'this/current/path/lastdir', instead look for /index.php?q=taxonomy/term/lastdir', and stop processing rules for this request ([L] for last).

This causes drupal (index.php) to look for a page or node that maps to drupal path 'taxonomy/term/[tid]', where [tid] is the part of the path after the last slash, or the tid of the current term. Global redirect intercepts this and redirects to the url_alias for taxonomy/term/[tid], which was probably set by pathauto when the term was created, or when pathauto mass generated url_aliases.

This method unfortunately means that taxonomy menu can no longer set the active term with <li class="active">. As menu.module can no longer see what path through the (taxonomy_menu) menu was taken to get to this menu item. To be able to do that, a change is being made to menu.module in drupal 6: http://drupal.org/node/103539. However I recently heard that hx is rewriting menu.module for d6. I'm not sure if/how this will affect peterx's patch.

For the above reason we've undone the hack described here in my client's site. You might find it useful for how the modules are configured though: http://www.bwmsnow.co.nz. We're using DHTML menu on the taxonomy menu, so defining the active menu item is necessary in the 'shop' taxonomy menu. For many other sites, especially if the taxonomy menu is working on a flat vocabulary, like the 'brand' taxonomy menu, this hack might still be useful though.

Interesting. Not sure why it only worked without [L].

Please read my first post starting this thread -- actually the whole thread... I wouldn't try and run this on your site, it needs a lot of work, and there are better solutions coming from other peoople anyway...

Hi, not that I know of, although we're not implementing this system, so I haven't tested it extensively