A) Menu Path Type:custom type
1) When choosing a "Display Depth in Custom Path: p.e. =3" and "Auto Expand Menu Item" is unchecked only the vocabulary level will be shown.
When "Auto Expand Menu Item" is checked the complete hierarchy will be shown.
2) When changing "Display Depth in Custom Path:" to other values no changes happen to the menu itself - the argument in url path seems to be correct.

B) "Hide Empty Terms" is checked (problem seems to be independend from "Dispay Descendants")
Terms are not shown that have no own node linked to it but have subterms that do have (so this menu trail should be shown - or not?)
Example:

category
-term1 (0)
-- subterm1 (12)
-- subterm2 (4)
-term2 (5)
--subterm3 (0)
--subterm4(1)

I think that if "Hide Empty Terms" is checked term1 should be shown, only subterm3 should not be shown. Or we would need another switch to decide those cases.

C) "Display Number of Nodes" is checked
Unchecking doesn´t change menu - even when rebuilt is checked or menu is disabled and then enabled again.

Thanks, Klaus

Comments

ksc’s picture

One more info:
Breadcrumbs seem to be fine.
The option "Set the breadcrumb for the term parents" for the first argument in views has to be disabled.

indytechcook’s picture

Thanks Klaus. I'll take a look at these. I had a feeling B might happen that way. It's not supposed to. It should show a parent when the children have nodes.

A2: This is what is supposed to occur. Did you mean something different for the option?

ksc’s picture

With A1 I mean that there are no terms under vocabulary at all. So when I klick on vocabulary no lower levels are shown.

indytechcook’s picture

I have some resolutions

A1: I figured out that the number of arguments in the view, have to match the number of arguments in the taxonomy menu path. To use depth change the path in the view to 'category/%/%'

B. Fixed in latest Dev. This was a tougher one. I had rewrite it a few times. I ended up checking to see if any of the children terms (of the term I was evaluated) had any noes attached to them.

C. Fixed. I had the code where I set the name in the wrong if statement :) This was an easy one.

Great catches an usually. You are a big part of making this module better.

ksc’s picture

A) Yes, you are right
B) I already thought that would be the only way.
C) ok.

Some more (no bugs!! :-)

D)
IF Display Depth in Custom Path=0
Argument 'Depth Modifier' is not shown within URL path.
[I know that´s nearly a philosophical question but I would suggest to write in the path whatever people enter in that field.]

E) [These explanations might reduce the numbers of mails you get]
Explanation text for "Base Path for Custom Path:"
Only used with a Custom Path. You need to have a view with path 'custom path/%' and an argument 'Term ID' before you create this taxonomy menu.

Explanation text for "Display Depth in Custom Path: "
"Only used with a Custom Path. To use depth the path in the view has to be 'custom path/%/%'" The two arguments must be 'Term ID (with depth)' and 'Depth Modifier'. Have this view setupbefore you create this taxonomy menu. Otherwise leave this field empty!

F) README FILE:
1)
CCK Content Taxonomy field
When using the CCK 'Content Taxonomy' module the field option Save values additionally to the core taxonomy system (into the 'term_node' table)' has to be enabled. Otherwise nodes with taxonomy terms linked through this field will not be shown within the menu structure that Taxonomy Menu creates.

2)
The part: ""VIEWS WITHOUT USING DEFAULT PATH" needs to be rewritten.

-> VIEWS WITH MENU PATH TYPE: DEFAULT
The default view is 'taxonomy_term (default)'. The path of the view is 'taxonomy/term/%', the argument is 'Term ID (with depth)' and 'Depth Modifier' - but only TERM ID will be passed as an argument.
This view can be changed - but it is recommended to use the option MENU PATH TYPE: CUSTOM for individual views.

-> VIEWS WITH MENU PATH TYPE: CUSTOM
You need to have a view with path 'custom path/%' and an argument 'Term ID' before you create the taxonomy menu.
To use the 'Display Depth in Custom Path:' option, the path in the view has to be 'custom path/%/%'" The two arguments must be 'Term ID (with depth)' and 'Depth Modifier'. Have this view setupbefore you create the taxonomy menu.

G)
When I get your latest dev-version I´ll do some investigations how 'Dispay Descendants' go along with 'Display Depth in Custom Path: = 1 or 0 ...' Maybe that users need to have some explanations at this point.
---------
So far -- Klaus

ksc’s picture

Oh, one thing!
->F1:
The name of the module is 'Content Taxonomy'.

I just read that there are four different modules dealing with Taxonomy and CCK:
http://drupal.org/node/212834
One module is called CCK taxonomy fields (only drupal 5.x), which I don´t refer to.
There is another module: http://drupal.org/project/taxonomy_super_select
I´ll see if I find some time to check weather this one works with tax_menu or not.

indytechcook’s picture

Thanks for the updated doc suggestions. I was going to work on compiling that info tonight and release another beta. Updating documentation is always the last thing I do (if at all sometimes- That's the BAD DEVELOPER in me!)

Good documentation can go a long way for the success of the module. I also plan on updating the book page (http://drupal.org/handbook/modules/taxonomy_menu) when I release the first stable version.

As long as the other modules are calling the core taxonomy functions to add/edit the taxonomy of the nodes then I will catch all of them. If they keep info in their own tables or do direct SQL calls then there isn't' anything I can do. But I do agree that the testing is needed if only for documentation purposes.

ksc’s picture

Hi Neil,
the latest dev version seems to be ok.
Only D) is open.

So I think, it is ready for the next beta stage.

Thanks Klaus

indytechcook’s picture

Status: Active » Fixed

Changes are in Beta2. So exciting!

ccshannon’s picture

I'm using Beta 2 and have the following problems:

First, I am testing using a small vocabulary called "Products".

Products has 3 parent terms: Hats, Bags and Accessories.

Accessories has 1 child term: Wallets

I install Taxonomy Menu. I DO NOT install the two additional modules for custom and hierarchy, for I just want to see the default behavior.

I create an empty menu for testing: TEST PROD MENU 1

I go to Taxonomy settings and edit Vocabulary "Products".

Menu: TEST PROD MENU 1
Menu Path Type: Default

I check the following, leaving the other options unchecked:

- Syncronise changes to this vocabulary
- Dispay Descendants (which sounds like I'm taking my kid's allowance back)
- Select to rebuild the menu on submit.

I Save changes, and get this:

* user warning: Table 'gallerieh.taxonomy_menu' doesn't exist query: SELECT mlid, tid FROM taxonomy_menu WHERE vid = 1 in /Users/cshannon/Sites/gallerieh.com/sites/all/modules/taxonomy_menu/taxonomy_menu.database.inc on line 45.
* user warning: Table 'gallerieh.taxonomy_menu' doesn't exist query: SELECT mlid FROM taxonomy_menu WHERE tid = 0 AND vid = 1 in /Users/cshannon/Sites/gallerieh.com/sites/all/modules/taxonomy_menu/taxonomy_menu.database.inc on line 32.
* user warning: Table 'gallerieh.taxonomy_menu' doesn't exist query: INSERT INTO taxonomy_menu (mlid, tid, vid) VALUES (884, 1, 1) in /Users/cshannon/Sites/gallerieh.com/sites/all/modules/taxonomy_menu/taxonomy_menu.database.inc on line 22.
* user warning: Table 'gallerieh.taxonomy_menu' doesn't exist query: SELECT mlid FROM taxonomy_menu WHERE tid = 0 AND vid = 1 in /Users/cshannon/Sites/gallerieh.com/sites/all/modules/taxonomy_menu/taxonomy_menu.database.inc on line 32.
* user warning: Table 'gallerieh.taxonomy_menu' doesn't exist query: INSERT INTO taxonomy_menu (mlid, tid, vid) VALUES (885, 2, 1) in /Users/cshannon/Sites/gallerieh.com/sites/all/modules/taxonomy_menu/taxonomy_menu.database.inc on line 22.
* user warning: Table 'gallerieh.taxonomy_menu' doesn't exist query: SELECT mlid FROM taxonomy_menu WHERE tid = 0 AND vid = 1 in /Users/cshannon/Sites/gallerieh.com/sites/all/modules/taxonomy_menu/taxonomy_menu.database.inc on line 32.
* user warning: Table 'gallerieh.taxonomy_menu' doesn't exist query: INSERT INTO taxonomy_menu (mlid, tid, vid) VALUES (886, 3, 1) in /Users/cshannon/Sites/gallerieh.com/sites/all/modules/taxonomy_menu/taxonomy_menu.database.inc on line 22.
* user warning: Table 'gallerieh.taxonomy_menu' doesn't exist query: SELECT mlid FROM taxonomy_menu WHERE tid = 3 AND vid = 1 in /Users/cshannon/Sites/gallerieh.com/sites/all/modules/taxonomy_menu/taxonomy_menu.database.inc on line 32.
* user warning: Table 'gallerieh.taxonomy_menu' doesn't exist query: INSERT INTO taxonomy_menu (mlid, tid, vid) VALUES (887, 11, 1) in /Users/cshannon/Sites/gallerieh.com/sites/all/modules/taxonomy_menu/taxonomy_menu.database.inc on line 22.

Yes, I'm doing this on my Mac, in case you were wondering. I go into the mysql DB and, as expected, there is no taxonomy_menu table. Should there be?

The resulting block is a mess:

TEST PROD MENU 1

* Hats
* Hats
* Hats
* Hats
* Wallets
* Wallets
* Wallets
* Wallets
* Bags
* Bags
* Bags
* Bags

Note that the number of term mentions is 4 each and are not indicative of actual nodes' terms. Right now I have:

Hats (6 nodes)
Bags (4 nodes)
Accessories (1 node)
Wallets (2 nodes)

What I'm trying to achieve would like this expanded:

Hats
Bags
Accessories
- Wallets

Any ideas?

indytechcook’s picture

There should be a table. It's part of the install process. Did you receive any errors when you install it? Did you have the previous version? If so make sure you do an uninstall of the previous version first (not just unchecking the box in the module list).

ksc’s picture

I tried to reproduce your problem.
Empty menu
Vocabulary with parent and one child level
Same taxonomy menu options
- no problem.
In my database there is a taxonomy_menu table.

Have you had the taxonomy menu dev-version installed before?
If yes, did you deinstall or just update?

Klaus (another user)

ccshannon’s picture

Ah, ok. Thanks for the quick response, all, I knew I missed a step.

I forgot to go to modules/uninstall after i disabled it and before i trashed the folder.

Went back, did the uninstall, trashed the folder, put in a fresh one, re-enabled. Table is created.

Now, when I populate the Test Menu, I get this:

- Hats
- Bags

There's something about my parent term "Accessories" which has one child term "Wallets" that it either doesn't like or I am not to use parent terms under the Default type. To review, I have one product (node) listed as "Accessories" and two products listed as "Wallets", so currently no terms are "empty". Even so, I do not have "Hide Empty Terms" enabled.

Is that the expected behavior? Does this mean I should enable hierarchy and/or custom?

The good news is, it picked up my pathauto settings just dandy, just not all my terms.

ccshannon’s picture

Checked mysql DB.

Browsed the table taxonomy_menu.

All the terms are listed i the table:

1 (hats)
2 (bags)
3 (accessories)
11 (wallets)

but the last two do not show up in the menu. I created one more child term for accessories, left it empty. Still, I only get

- Hats
- Bags

I look in the taxonomy_menu table, and I see all 5 term IDs listed.

So, it's getting into the DB but Accessories and its child terms are not accessible on either the Menus builder or the Block for the Menu.

Should I create a new thread for this, given this thread is marked as "fixed"? Thanks, again for all the work being done on this module.

indytechcook’s picture

I'm not sure I follow. Something doesn't sound right Please elaborate so I can see if I can reproduce.

Please break down the detail of your vocabulary

example.

vocab
-term 1
-term 2
--term3

What settings you have selected in taxonomy Menu.

indytechcook’s picture

Please post this into a new new thread also and the extra information.

ccshannon’s picture

Thanks.

Products
-Hats
-Bags
-Accessories
--Wallets
--Scarves

Vocabulary = "Products"
Term 1 = "Hats"
Term 2 = "Bags"
Term 3 = "Accessories"
Term 11 = "Wallets" (child term of Accessories)
Term 12 = "Scarves" (child term of Accessories)

Number of nodes assigned each term:

Hats (6)
Bags (4)
Accessories (1)
Wallets (2)
Scarves (0)

I create an Empty Menu called "Tax Menu Test".
I go to Edit Vocabulary for "Products".
Menu: "Tax Menu Test"
Menu Path Type: Default

I check the following:

- Syncronise changes to this vocabulary
- Dispay Descendants
- Select to rebuild the menu on submit.

I Submit. I go to Blocks. I enable "Tax Menu Test" block.

I see this:

- Hats
- Bags

So, "Accessories" and its children are not shown.

ccshannon’s picture

More weirdness:

I created a "dummy" term, parent is and called it "Dummy".

"Dummy" with zero nodes using the term, shows up in the menu.

I move "Wallets" from under "Accessories" and to "Dummy".

Now I see:

-Dummy
--Wallets
-Hats
-Bags

and that's it.

Then I move "Scarves" under "Dummy" and see:

-Dummy
--Wallets
--Scarves
-Hats
-Bags

Remember, I still have one node with term "Accessories" so I go to that node, and remove its Product term. now I get:

-Dummy
--Wallets
--Scarves
-Hats
-Bags
-Accessories

Moved Wallets and Scarves back under "Accessories" and got:

-Hats
-Bags
-Accessories
--Wallets
--Scarves

Yup, "Dummy" which is still there, disappeared. Re-edited Product node (that now has no term) and put back term "Accessories".

-Hats
-Bags
-Accessories
--Wallets
--Scarves

"Dummy" is still missing. This is kind of maddening.

ccshannon’s picture

Just to condense what I've posted into something concise:

No matter how I adjust my taxonomy terms, with the 6.x-2.x-dev of Taxonomy Menu, I always have one term "missing" from both the Menu Block and from the Menu admin page for the Taxonomy Menu-driven menu. If that particular term has child terms, those will also be "missing".

The taxonomy Id's are indeed being inserted properly into the taxonomy_menu table, but not into the menu_links table.

I will turn on query logging and see if I can figure out why terms are being skipped. I'm not getting any DB errors, though.

This could always turn out to be something amiss on my system, and not the module itself, of course.

ksc’s picture

My suggestion is:
Deinstall (not just uncheck under module) the taxonomy menu module! Delete the files.
Delete your taxonomy terms and vocabulary
Create a new vocabulary with the terms you had.
Edit your nodes and select the taxaonomy terms.
Install taxonomy menu latest beta version.

I guess that´s shorter than to experiment with other solutions

Klaus

ccshannon’s picture

Thanks, Klaus. I think removing the vocabulary and re-entering it is a good plan. -C

Status: Fixed » Closed (fixed)

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