After unchecking "Cache menu in client-side browser", checking a few Developer modules to keep enabled and then submitting, I'm getting this error on the admin pages for admin_menu:

Notice: Undefined index: name in admin_menu_theme_settings() (line 708 of /.../sites/all/modules/admin_menu/admin_menu.inc).

This is on a fresh install with only a few modules enabled outside of core like views, ctools, fontyourface.

CommentFileSizeAuthor
#3 admin_menu-1997386.patch555 bytessweetchuck

Comments

Anonymous’s picture

Anonymous (not verified) commented

Getting the same error.

Discovered it's referring to the 'bad' sub-module of Coder. Similar issues relating to the missing name value were addressed by the Coder team by adding hidden = TRUE to bad.info.

Admin Menu, however, still displays hidden modules; hence the error. I recommend Admin Menu does something like what system_modules() does and ignores hidden modules:

// Remove hidden modules from display list.
$visible_files = $files;
foreach ($visible_files as $filename => $file) {
  if (!empty($file->info['hidden'])) {
    unset($visible_files[$filename]);
  }
}
kanenas’s picture

kanenas commented
Version: 7.x-3.x-dev » 7.x-3.0-rc4

I am experiencing this "Notice"...

Notice: Undefined index: name in admin_menu_theme_settings() (line 708 of /path/to/file/sites/all/modules/admin_menu/admin_menu.inc).

just by accessing "admin/config/administration/admin_menu".

sweetchuck’s picture

sweetchuck
Primary language Hungarian
Location Budapest
commented
Status: Active » Needs review
StatusFileSize
new admin_menu-1997386.patch555 bytes
alan d.’s picture

alan d. commented
Issue summary: View changes
Priority: Normal » Minor
Status: Needs review » Reviewed & tested by the community

Looks good to me, I was about to write a patch for the same notice ;)

mfuller526’s picture

mfuller526 commented

3: admin_menu-1997386.patch queued for re-testing.

mfuller526’s picture

mfuller526 commented

User error: patch AOK!

jfrederick’s picture

jfrederick commented

#3 worked for me.

euk’s picture

euk commented

#3 worked for me as well!

gngn’s picture

gngn commented

#3 worked for me as well, thank you!

Running the patch and checking what it actually does, I noticed that on my system there are more than 80 modules skipped because they are set to "hidden".

The array $all_modules is just used to find the "devel modules" with array_intersect_key().
Since array_intersect_key() just uses the keys, we could also:

  • check for isset($info['name'])
  • and use $all_modules[$module->name] = $module->name; if it's not.

That way (again on my system) only one module is skipped - the above mentioned 'bad' sub-module of Coder.

What do you think? I could supply a patch if anyone's interested.

euk’s picture

euk commented

I may be a good thing.
Give us a patch )

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Reviewed & tested by the community » Closed (won't fix)

The 'disable development modules' functionality has been removed as of #2392519: Remove 'Disable Development modules'.

alan d.’s picture

alan d. commented

Third time checking this, this should be in the latest RC version.

Issue #2392519 was committed on the 16th Dec, a few days before 7.x-3.0-rc5 (19th)