Hi!

Despite the several bugs(errors) I've been dealing of, as refered by many others, I've managed to overcome some issues by adding the Menu Breadcrumb Module [Drupal6.19].
However, I can't make exact crumbs for core modules such as Blog or Forum when they are in a child menu position...
For example, the breadcrumbs given for the menu path SUPPORT > FORUM is HOME > FORUM instead of HOME > SUPPORT > FORUM.

How can I solve this?

Thanks!

Comments

sun’s picture

Status: Active » Closed (won't fix)
Issue tags: -blog, -code, -breadcrumbs, -patch, -Forum, -modules, -core

This issue does not seem to be related to the functionality of this module. Therefore, closing this issue. See http://drupal.org/support for support channels.

Feel free to re-open this issue if I'm mistaken. Thanks.

klonos’s picture

Project: Breadcrumb » Menu Breadcrumb
Version: » 6.x-1.3
Component: Code » Miscellaneous
Assigned: xpound » Unassigned
Status: Closed (won't fix) » Postponed (maintainer needs more info)

...actually this is for Menu Breadcrumb, so switching to that project's queue where it belongs/belonged.

@xpound: Carlos, are you still having this issue? Please take some time to follow this up (either that or close it). Anyways, setting it to postponed till you do something about it (I guess it will most likely be closed soon if you don't act, since you originally filed this on November last year).

You mention that you were using D6.19. That fact + the date the issue was filed "smells" like version 6.x-1.3 of the module. Finally, the support request seems to me that has little to do with code, so switching to a more generic component and unassigning it from you (you should only assign issues to yourself if you intent to do something about them / work on them).

/ just trying to help clearing up the issue queue here /

xurizaemon’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

Cleaning up issue queue. Closing all D6 issues.

If you believe this issue still applies to a supported version, feel free to re-open it. That would be a great time to check if the issue contains clear steps for reproducing the bug!

Thanks and sorry for any inconvenience.