Hello,

I've used this module recently and it's no fun having to apply all the patches from the bug tracker just to get the basic functionality to work. The last commit has been nearly 4 months ago, the last code commit was about 7 months ago.

If this module is no longer maintained I would like to take over maintaining. I've read every line of code, had to hack new features into it, and fixed a couple of bugs already(originally intended for my personal use so they aren't the highest quality, just good enough to get *my* job done)

Kind Regards,
Afief

Comments

hutch’s picture

hutch commented

I would like to express my support for this proposition, I have a number of D5 sites where I have had to freeze taxonomy_menu to the dev version of June 19 2007 which although very basic does work.
This is an important module and it needs to be revitalised.

Hope this helps.

ThePiano.SG’s picture

ThePiano.SG commented

I am using this module as well, and I believe if someone can patch it to perform better, why not, as long as the history of contributions is maintained to give credit to past contributors.

ss_drupal’s picture

ss_drupal commented

I vote yes. Enthusiastically. I want to move new projects to Drupal 6 for the sake of better internationalization. But right now the major impediment is getting solid with taxonomy menu.

I'm not adept at module changes, but critically need to get meaningful keyword links working with this module, pathauto style. I've been seeing discussions of this shortcoming for months, but haven't located a patch for V6. I'm desperate enough to try to do the work myself, but have no confidence that I'll produce anything up to general use standards.

Two things:

1) Afief says above "it's no fun having to apply all the patches from the bug tracker just to get the basic functionality to work". Do you have a handy list of what those are?

2) There seems to be a confluence of unrelated problems that stand in the way of a solid well internationalized and categorized site that is consistently seo friendly.
-- The taxonomy menu nid link style.
-- The i18n issue with Global Redirect

I wonder if this is worth a forum subject?

Afief’s picture

Afief commented

Guys, this isn't a vote. Drupal guidelines state that if someone is interested in taking over a (seemingly) unmaintained module he/she should open this kind of issue and give the original maintainer two weeks to reply(The original maintainer might be busy with something else and planning to get back to this module...)

ss_drupal:
1. Sorry I don't. I recall a patch that fixed the menu permissions and a patch printing the breadcrumb and not just "Array". I had to add a patch that added the option "Don't show sticky nodes from descendant taxonomy terms" under "show descendants" and another enabling the module to turn all taxonomy terms into menu items regardless the language.
As I said my work isn't the most gracious as I was under time pressure to fix those issues and never planned on publishing anything.

2. the nid link style is something that can be easily fixed(if memory serves well) but all menu items for the same category would still have links in only one language. That means /categories/table won't turn into /categories/tisch if you're on the german version of the site(at least not with this simple solution. If there is.
I am unfamiliar with the Global Redirect module, but if it has trouble integrating with i18n then their issue queue is the place to post(I might have terribly misunderstood this, if so please elaborate)

ss_drupal’s picture

ss_drupal commented

Sorry about the seeming misunderstanding. I know it's not a vote. I just meant to lend some moral support.

Re. Global Redirect & i18n, it's a known issue documented on the Global Redirect project page.

What I meant to do was to comment on what seems to me to be a general need, and what seem to be some related limitations or problems.

I'm sure there are numerous situations, beside my own coming projects, that have the following requirements.

*Good category guided navigation -- a natural job for taxonomy menu (and DHTML Menu)
*SEO friendliness -
    keyword structured rather than nid structured taxonomy menu links & pathauto
    no duplicated content - Global redirect
*Multilingual
    i18n etc, translated content, (BTW Localization client is terrific!)
    multilingual taxonomy
    -- ideally speaking -- multilingual taxonomy menu
    -- and ideally ideally, pointing to the appropriate translated content or defaulting to the
    locale default language content

All of this is rather ambitious and, I fear, beyond my meager php and drupal skills. But I can't imagine that I am alone in confronting this set of requirements. They just seem too generic and common-sensical to be unique to my projects.

What I'm wondering is whether other folks here see the same need (for the same complex of requirements) and think it worth coordinating around the issue.

=============

Back to the main topic:

To the best of my knowledge there's only 1 patch to move from category/1/2/3 style links to category/term1/term2/term3 style links, and that patch is only for V5 and doesn't address the breadcrumb issue.

I believe that patch is here: This patch does not care about node breadcrumbs.

I'm half thinking of reverting to V5 for the sake of using that patch, unless I can find a way to get the link style issue handled on V6.

If you know the answers, would you tip me off to where and roughly how I should alter the existing code to at least get the menu properly expanded and fix the link issue. It would be a start.

V6 seems to have more and better multilingual stuff and other desirable goodies, so I hesitate to leave it. But Taxonomy Menu is too important.

kenorb’s picture

kenorb commented

I've similar problems with this module, any alternatives?

Afief’s picture

Afief commented

Sorry for the late reply, but better late than never

ss_drupal:

If you could come up with some precise examples for what kind of integration is needed for each module things would be much easier. I am sure people who build multilanguage sites *do* run into the same problems(I ran into a problem with multilanguage taxonomies myself) so fixing this should certainly be a priority.

I am not sure which patches I applied and what each of them looked like(quit my job, no longer have access to the customized module) and I didn't need to change the way my links look(hey most people here are fine with whatever sits in the link as long as the page appears), but the patch you referenced looks like it should work in D6 since it's just a function(if not you might need to copy some of the code from taxonomy_menu_menu to get the correct data structures)

I am not aware of the "properly expanded" issue you mentioned. Examples?

PS: Looks like there are so many issues/feture requests for this module that setting up something similar to Dell IdeaStorm...

kenorb:
I am not aware of any alternative module.

petertj’s picture

petertj commented

subscribing... we'd also like to see this module brought up to date for 6.x. The main thing that's not working in current 6.4 is the subcategories, seem to be several duplicate issues related to that topic.

Afief’s picture

Afief commented
Project: Taxonomy Menu » Drupal.org site moderators
Version: 6.x-1.0 »
Component: Code » Project ownership

This module(Taxonomy Menu) seems to be unmaintained. I would like to take over ownership of this module if it is possible.

Link to the module: http://drupal.org/project/taxonomy_menu

PS: I hope I did everything according to procedures.

vlad.leo’s picture

vlad.leo commented
Title: Taxonomy Menu still being maintained? » Taxonomy Menu appears to be abandoned!

Module (http://drupal.org/project/taxonomy_menu) is abandoned.

The maintainers haven't replying to issues for the past few months or so, and the last commit was in 2008-Apr-15, despite there being a number of patches in the queue (for examle http://drupal.org/node/231884 and http://drupal.org/node/282608)

August 22, 2008 we post topic Taxonomy Menu still being maintained? and nothing happen.

User Afief (http://drupal.org/user/237472) would be willing to become a co-maintainer if the current maintainers would like some help. Maybe you can made two maintainers for this project.

AjK’s picture

AjK commented
Status: Active » Fixed

Since the current maintainer hasn't responded to this thread project transferred to Afief. Original maintainer still on the CVS access list however.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

Project: Drupal.org site moderators » Drupal.org project ownership
Component: Project ownership » Ownership transfer