After upgrading from drupal 5 with image 5.x-1.9 to drupal 6 with image 1.0-beta3 i noticed a very strange behaviour:

In my case, i got a node eg. flowers as a menu entry with some galleries as its children.
After clicking on "node flowers" all children items appear like exspected but when clicking one of children, eg. image/tid/$roses it collapses while it works with a node a child element.

If i do the same with image/tid/$flowers instead of "node flowers" as menu parent item it doen't exspand at all even if one of the child elements is a node.

These behaviours are independent to system path's or aliases and my template.php file.
Note, all menu entries were created manually.

Comments

joachim’s picture

So just to get this right:

you have a menu like this:
- node/xx
-- image/tid/yy
-- image/tid/zz

and when you're at one of the galleries, the menu hierarchy doesn't work.

I think this is a shortcoming of Views and the D6 menu system. What you're seeing now at image/tid/yy is a view page display with an argument. I'm not sure how well they play in the menu system.

fl3a’s picture

Right,
and when i got

- image/tid/xx
-- node/xx

or

- image/tid/xx
-- image/tid/xx

or when doing the upgrade from drupal 5 and image 5.x-2.0-alpha4
and whether views is enabled or disabled

the same...

joachim’s picture

The same with Views disabled?
In which case, it's Drupal core weirdness -- you might need to rebuild your menu cache.
What happens when you try this menu structure on an 6 site that's not been upgraded from 5?

fl3a’s picture

Yes, independant to views and of cause i had cleared the menu cache on the updated site.
But on a fresh d6 site

- image
-- image/tid/xx

works.
But the rest as same as above, seems to be impossible to have image/tid/xx or a node as sub of a image/tid/xx, same with image/tid/xx as sub of a node...

sun’s picture

Status: Active » Closed (works as designed)

That's a limitation of the menu system in Drupal 6.