Download & Extend

icon_users as page title on user login and admin pages

Project:Administration menu
Version:6.x-1.5
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (duplicate)

Issue Summary

When both admin_menu and rootcandy are installed, when visiting the Users admin page at /admin/user/user, you get <img src="/sites/all/modules/admin_menu/images/icon_users.png" width="16" height="15" alt="Current anonymous / authenticated users" title="Current anonymous / authenticated users" /> in the title.

See #279767: User counter is output on login page for anonymous users (with a potential solution at #27).

Comments

#1

Status:active» postponed (maintainer needs more info)

I can't replicate this with admin_menu 1.5
what version of admin_menu are you using?

#2

Version:6.x-1.2» 6.x-1.1

I'm getting the same issue. I was brought on by a client to finish a site. We're using admin_menu 1.5, but not rootcandy (the form forced me to choose a version). It really is not a particularly complex site. The client says that this error only came up recently. Mostly all I did was add some content types and Views for them. One of the Views has some php snippets for the View header. If I disable the admin_menu module, then I get the normal page title. Note that the attribute is similarly affected, so the img tag shows in the browser tab as well as the page title. So far I can't find any other pages so affected, just admin/user/user.

I've attached a screenshot of the relevant parts of the screen.

AttachmentSizeStatusTest resultOperations
title_problem.jpg50.78 KBIgnored: Check issue status.NoneNone

#3

Project:RootCandy» Administration menu
Version:6.x-1.1» 6.x-1.5
Status:postponed (maintainer needs more info)» active

So I would say this is not a rootcandy issue, but appears to be an admin_menu issue

I am moving this to admin_menu project and lets see if @sun agree

@drm btw your screenshot is not appearing

#4

The title 2 / 0 <img src="/sites/all/modules/admin_menu/images/icon_users.png" width="16" height="15" alt="Current anonymous / authenticated users" title="Current anonymous / authenticated users" /> also appears on the user login screen, which is not on the RootCandy theme, so yes, it appears to be the Admin Menu module causing the problem, especially as the problem vanishes when that module is not installed.

Using Administration menu 6.x-1.5 on Drupal 6.13.

#5

Title:icon_users as page title when installed with admin menu» icon_users as page title on user login and admin pages

changing title to reflect issue

#6

The theme we're using is based on Zen, btw, so if it's the theme, I'll move it to that queue. Still investigating.

#7

no, happens on garland too.

#8

Status:active» closed (duplicate)

ok, on further investigation (and actually reading #279767: User counter is output on login page for anonymous users), I see this is actually #303247: Menu Breadcrumb setting active menu to undesirable menus for menu_breadcrumbs. Marking this as duplicate.

#9

Subscribing.

#10

I have this issue, but DO NOT have Menu Breadcrumb installed. Thinking it could be the Menu Position module, as this does some breadcrumb setting with menu items.

#11

I'm also getting this issue without Menu Breadcrumb installed. I do not have Menu Position installed either.

#12

Perhaps you meant to write that the other way?

#13

Same issue, but I am not using any of the above mentioned modules.

#14

#15

This issue is caused by having dual entries for the same path in the menu (router?) tables. A module will go looking for a path and find the wrong one (similar, but different?!) and this is what causes it.

You can get a vague idea of what's going on from reading here: http://drupal.org/node/303247 (menu_breadcrumb module problem) and comment #23 onwards (or before if you fancy) for Sun's opinion on the admin_menu side of it at http://drupal.org/node/279767.

Rootcandy might be demonstrating this problem, but it's basically like this... admin_menu is the root cause of it, becase that's where the duplicate paths come from, but that module isn't what makes the problem occur. The modules that expect the paths to be unique are what force the problem out into the open, and that's because they have wrongly assumed the path(s) to be unique. You need to modify your query according to the advice in those issues and it should be sorted.

HTH

nobody click here