After installing the DHTML menu module for Drupal, I noticed that the Catalog block was not working with DHTML. After a little research on the Ubercart forums, I noticed that the Catalog block is not using the Drupal menu API to generate the links. I guess my suggestion is move the menu generation to the Drupal API in order to enable the DHTML functions on the Catalog block.
I'm considering beginning work on this. I found the thread in Ubercart.org but not here so I felt like I should add it. Cheers.
Comments
Comment #1
nickcaballero commentedRelated DHTML Menu Bug Report: #352005: Ubercart DHTML conflict - use module-specific selector
Related Ubercart Suggestion: uc_catalog: Use the menu API for generating menu blocks
Comment #2
nickcaballero commentedDHTML Menu bug fix for the Catalog block only prevents the handling of the Catalog block as a DHTML menu.
Ubercart forums reveals various fixes using Taxonomy Menu and Views. Seems like a viable fix but DHTML menus in the Catalog block seems lacking - I almost took it for granted when I first installed.
Comment #3
rszrama commentedYeah, at this point I'd recommend Taxonomy Menu if possible. It's what I've used to replace the catalog block on sites.
Comment #4
nickcaballero commentedI tried to use Taxanomy Menu and it is a good solution. Nonetheless, using the menu API seems like the right approach. I think I'll start to work on this because it seems like a feature that should have been integrated from the beginning.
Comment #5
tr commentedMoving to 7.x-3.x.
Comment #6
longwaveI don't see how this can be done in D7. Catalog menu items are /catalog/N where N is the term ID, we would need to reorganise this into a hierarchy of /catalog/A/B/C/D where D is a child of parents C, B, A for it to work in the standard Drupal menu structure - but then I don't see how that would be compatible with using Views arguments to display the relevant page. Perhaps possible in D6, but not worth changing now.