Closed (fixed)
Project:
Node breadcrumb
Version:
6.x-1.0-beta5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Jan 2009 at 14:51 UTC
Updated:
5 Nov 2009 at 11:40 UTC
When the the Node Breadcrumb and Admin Menu Module are enabled at the same time the following code is printed at the top of the user login page (example.com/user):
[code]
1 / 0 ![]()
[/code]
Here is the link to the related issue for Admin Menu: http://drupal.org/node/279767
Attached is a screenshot.
| Comment | File | Size | Author |
|---|---|---|---|
| userlogin.png | 18.22 KB | codybarr |
Comments
Comment #1
codybarr commentedSorry:
1 / 0 <img src="/sites/godbyte.com/modules/admin_menu/images/icon_users.png" width="16" height="15" alt="Current anonymous / authenticated users" title="Current anonymous / authenticated users" />Comment #2
kevinquillen commentedIs this fixed yet or what?
Comment #3
codybarr commentedNo, this problem still persists.
Comment #4
mpettitt commentedChanging the node_breadcrumb_init function as shown below (based on patch at http://drupal.org/node/303247#comment-1310764) _seems_ to work, but I've not tested extensively, hence no actual patch. Also, this doesn't make any attempt to make the changes configurable, since I just needed it working, not looking pretty!
Comment #5
kevinquillen commentedI changed menu breadcrumb (problem is in there too) in its menu sql to exclude names containing 'admin_menu'.
Fixed it wonderfully.
This should be added into the module!
Comment #6
jacineWas having the same issue, but applying #4 fixed the problem ;)
Comment #7
peter.walter commentedSeeing same problem - changed line 59 of node_breadcrumb.module from
menu_set_active_menu_name(db_result(db_query("select menu_name from {menu_links} where link_path='%s'", $menu_item['href'])));to
menu_set_active_menu_name(db_result(db_query("select menu_name from {menu_links} where menu_name != 'admin_menu' AND link_path='%s'", $menu_item['href'])));Worked for me.
Peter
Comment #8
AkkuDreamz commentedthanks Peter
thats fixed it for me too
:)
Comment #9
brad.bulger commentedjust confirming this is still a problem - it seemed like the beta5 release had fixed it, at first, but then there were other problems with that release, and moving to 1.x-dev solved the other stuff but brought this problem back. the patches described above work fine in the meantime.
Comment #10
edhel commentedfixed in beta6
// 6.x-1.x-dev is very old, don't use it