Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
fresh local installation and that is what i've got. any idea?
Notice: Undefined index: name in system_sort_modules_by_info_name() (line 926 of /var/www/drupal-7/modules/system/system.admin.inc).
Notice: Undefined index: name in system_sort_modules_by_info_name() (line 926 of /var/www/drupal-7/modules/system/system.admin.inc).
Notice: Undefined index: name in system_sort_modules_by_info_name() (line 926 of /var/www/drupal-7/modules/system/system.admin.inc).
Notice: Undefined index: name in _system_modules_build_row() (line 959 of /var/www/drupal-7/modules/system/system.admin.inc).Notice: Undefined index: name in system_sort_modules_by_info_name() (line 926 of /var/www/drupal-7/modules/system/system.admin.inc).
Notice: Undefined index: name in system_sort_modules_by_info_name() (line 926 of /var/www/drupal-7/modules/system/system.admin.inc).
Notice: Undefined index: name in system_sort_modules_by_info_name() (line 926 of /var/www/drupal-7/modules/system/system.admin.inc).
Notice: Undefined index: name in _system_modules_build_row() (line 959 of /var/www/drupal-7/modules/system/system.admin.inc).
Comment | File | Size | Author |
---|---|---|---|
#36 | notice-undefined-index-939498-34.patch | 754 bytes | jyotisankar |
#34 | notice-undefined-index-939498-34.patch | 754 bytes | jyotisankar |
#15 | utf8_BOM.patch | 774 bytes | droplet |
#15 | utf8_BOM_for_bot_test.patch | 1.17 KB | droplet |
Comments
Comment #1
furamag CreditAttribution: furamag commentedHow can I reproduce this error? Can you provide URL where you saw this error?
Comment #2
datenrettung CreditAttribution: datenrettung commentedI've found the evil module.
http://drupal.org/project/libraries, Last updated: October 12, 2010 - 00:12, is the reason for this behaviour
so, it's NOT drupal7!!! sorry.
it's a local installation for testing.
"private" server without url = localhost
ubuntu 10.10
php 5.2
apache2
mariadb
Comment #3
furamag CreditAttribution: furamag commentedIf it's not Drupal 7 bug I think we should close this issue. You can see bug report for that issue on following page - http://drupal.org/node/939174 .
Comment #4
ifernando CreditAttribution: ifernando commentedI got the same error.
Check that $Id$ is properly commented with a semicolon (i.e., ;$Id$).
Comment #5
-ds- CreditAttribution: -ds- commentedFor anyone else coming across this error and ending up here via a search: This error is most likely to do with a custom module, in particular the module.info file.
Make sure you have it correctly formatted and if you have any comments in this file, be sure to use a semicolon at the beginning of comment lines, unlike usual php // comment markers.
Comment #6
RobAlex CreditAttribution: RobAlex commentedI got essentially the same set of error messages a few days ago with no custom module. I was, however, creating a Genesis sub-theme and did modify the sub-theme's info file. But the error messages persisted after I had disabled both the sub-theme and the Genesis theme. No other files were modified.
Later: I removed the sub-theme instead of just disabling it and the messages went away. So one has to watch one's disabled themes and modules as well as the enabled ones - a surprise to me.
And it was the theme's info file.
Comment #7
svinec CreditAttribution: svinec commentedI also got this error from a theme's .info file. First, I physically removed the theme from the folder (site/all/themes) and the error disappeared. Then, I went on to find out what was the cause. It turned out to be the .info file's encoding. The error appeared when using utf8 encoding. Problem solved (for me) using ANSI encoding.
(using Drupal 7.8)
Comment #8
fabul CreditAttribution: fabul commentedHi,
I met the same message after my first module was built. I resolved it when I suppressed the tag <?php at the beginning of my module file .info.
I hope this response is usefull.
KJ
Comment #9
r2integrated CreditAttribution: r2integrated commentedConfirming svinec's findings (#7) - this issue appeared when my *.info file was encoded in UTF8. Changed to ANSI and it works fine. I do not believe, in svinec's and my case, that this is a duplicate of http://drupal.org/node/939174. I'm guessing that file encoding shouldn't affect whether or not a .info file is loaded properly, correct? In case it helps when trying to reproduce the issue, this issue is reproducible with D7.12 on php 5.3.3 running under Windows.
Comment #10
damien_vancouver CreditAttribution: damien_vancouver commentedI was seeing this error on my modules list page, caused by an invalid
// Id$
line at the top of a module's .info file.Since it's not obvious which module is causing the problem, here is some debugging code to print out the module causing the error:
function system_sort_modules_by_info_name($a, $b) {
(this is line 925 in Drupal 7.12. The error message will also show you the approximate line.)
function system_sort_modules_by_info_name($a, $b) {
Comment #11
1mik3 CreditAttribution: 1mik3 commentedTo anyone who finds this from google or whatnot and is not a programmer, for me, i solved this error by deleting all the themes i uploaded and then re-uploading the one i needed and now everything is fixed.
Comment #12
droplet CreditAttribution: droplet commentedSounds like something wrong in #939174: Notices on the modules page (due to fake info file)
Comment #13
r2integrated CreditAttribution: r2integrated commented@droplet, please see my post (#9). I'm not sure this should be closed just yet. In my particular use case, I don't believe this is a dupe of 939174.
Comment #14
droplet CreditAttribution: droplet commentedLets test it.
Comment #15
droplet CreditAttribution: droplet commentedforgot attach files
Comment #16
Amit_Webgrity CreditAttribution: Amit_Webgrity commentedI got this errors.How to fix it in drupal7.
Please Help me.
Advance Thanks.
Notice: Undefined index: name in system_sort_modules_by_info_name() (line 944 of E:\wamp\www\cms\drupal\drupal-7.14\modules\system\system.admin.inc).
Notice: Undefined index: name in system_sort_modules_by_info_name() (line 944 of E:\wamp\www\cms\drupal\drupal-7.14\modules\system\system.admin.inc).
Notice: Undefined index: name in system_themes_page() (line 148 of E:\wamp\www\cms\drupal\drupal-7.14\modules\system\system.admin.inc).
Notice: Undefined index: name in system_themes_page() (line 166 of E:\wamp\www\cms\drupal\drupal-7.14\modules\system\system.admin.inc).
Notice: Undefined index: name in system_themes_page() (line 167 of E:\wamp\www\cms\drupal\drupal-7.14\modules\system\system.admin.inc).
Notice: Undefined index: name in theme_system_themes_page() (line 2728 of E:\wamp\www\cms\drupal\drupal-7.14\modules\system\system.admin.inc).
Comment #17
dcrocks CreditAttribution: dcrocks commented@AMIT You wouldn't happen to have a theme in your installation whose .info file doesn't contain a NAME specification? Look at #619542: Malformed theme .info files break menu_router generation.
Comment #18
mgiffordRelated issue - #1015368: Notice: Undefined index: name in system_sort_modules_by_info_name()
Patch didn't work for me, but I found what I think is the issue by searching my modules for
;$Id$
:grep -r '$Id' sites/all/modules/contrib/
Comment #19
littleindian CreditAttribution: littleindian commentedI got the same error when i was working with my coustom module.
I just edited my .info file .
In .info file i wrote in first
"cd name = module name"
then i changed it to "name = module name" and it worked that error gone.
I hope this will be helpful for you.
Comment #20
raynimmo CreditAttribution: raynimmo commentedCame across this post when encountered with a similar error whilst building a new module. I had about 20 lines of;
I also found that my new custom module and one other, didnt have their name displayed in the modules page although the entry was there with the enable checkbox. Even if i enabled the modules they did nothing.
This was a fresh development install of D7, all it had enabled was the main core modules and testing/development modules with the standard Bartik theme..
Tried a few of the solutions above and then noticed the post by r2Integrated above at #9 where he mentions the file encoding.
Earlier on today was playing around with a few different text editors, it appears that all of the files in my new module where now encoded as UTF-8, changed them all back to ISO 8859-1 and the errors went away.
This wasn't only affected by the modules .info file as that was the first file I changed back, only when I changed the rest of the files back to 8859-1 did it remedy the situation.
These changes brought back the entry for the new module into the main modules page but there was still one missing. I managed to track it down to the Test folder within /coder/coder_sniffer/ I then deleted that entire folder and the errors went away.
Ran cron, flushed the cache, all seems fine.
Hopefully my solution helps anyone else that comes across this problem.
Comment #21
iva2k CreditAttribution: iva2k commentedFile /coder/coder_sniffer/Test/bad.info is intentionally malformatted, so the code_sniffer tests can be run with a bad code example.
My 2 cents: system_sort_modules_by_info_name() function should guard from missing indexes and not throw warnings/errors. Elsewhere in system.module that same .info file does not make it onto the list of valid modules.
Comment #22
exvita CreditAttribution: exvita commentedI have a similar problem.
I updated from 7.16 to 7.18 today, and then I had below warnings.
And I had tried to change the format to ANSI as advise, but it seemed not working.
I'm quite new to dropal, so kind of stuck and don't know what to do now...
Comment #23
Ash07 CreditAttribution: Ash07 commentedI have the same problem too.
I made a Commerce Kickstart installation, and in administration / site settings / Advanced settings / Modules reports the following errors:
Comment #24
Ash07 CreditAttribution: Ash07 commentedI solved the problem by uninstalling and deleting the Coder module. Now everything is working properly.
Comment #25
droplet CreditAttribution: droplet commentedCoder contains a "bad.info". It's designed to be broken..
Comment #26
Ash07 CreditAttribution: Ash07 commentedThanks droplet
Comment #27
dustinsilva@gmail.com CreditAttribution: dustinsilva@gmail.com commentedI ran into the error as described by "datenrettung", and attempted to run 'flush all caches' which then caused this error:
And after browsing through
drush help
, I fixed the problem by running these two commands while in the root of the drupal install:drush cc
drush sapi-c
I also had to ensure the field 'item_type' in the 'search_api_index' table in mysql was set to 'node' (I tried setting it equal to the value in the field 'machine_name' with no luck.)
I am not exactly sure of the steps taken to land the error to begin with, but this fixed the secondary error for me.
good luck
Comment #28
droplet CreditAttribution: droplet commentedComment #29
marcoscanoI was having the same problem with a custom module, and after converting all my module files from "UTF-8" to "UTF-8 without BOM" the errors disappeared
Comment #30
rwilson0429 CreditAttribution: rwilson0429 commentedProblem began occurring for me after installing a custom module. Changing the encoding of the .info and the .module file from UTF-8 to ANSI (as stated in #7 and #9) resolved the issue for me.
Comment #31
ruchirashree CreditAttribution: ruchirashree commentedHi,
@ #10 Thanks a lot.
It helped me a lot to debug and find out which module was causing issue.
I hope it will help others too.
Comment #32
togbonna CreditAttribution: togbonna commentedI also discovered that this could be caused by a .info module file in which the required components (name and description) are left out, even if the module is not enabled.
In this case these notices occurs only in the modules listing page and the module causing the problem will not be listed at all.
In my case the culprit module was rrssb (Ridiculously Responsive Social Share Buttons). In addition to its main module it declared another module rrssb_views which has no code in the .module file and the required components of its .info file were left out.
Filling in the missing components with dummy texts made the problem go away in my case.
Comment #33
jhedstromPatch no longer applies.
Comment #34
jyotisankar CreditAttribution: jyotisankar commentedThe changes on the the function "drupal_parse_info_format()" not exist in drupal8. Applied the patch for drupal7
Comment #36
jyotisankar CreditAttribution: jyotisankar commentedComment #37
mgiffordApplies just fine on Drupal 7.34
What should be done to RTBC this patch? I'm not great with regular expressions but it seems to work fine.
I'm pretty sure this is right \xEF\xBB\xBF according to:
http://stackoverflow.com/questions/204765/elegant-way-to-search-for-utf-...
Comment #38
PlayfulWolf CreditAttribution: PlayfulWolf commentedWorks with 7.36, but patch has to be applied manually, lines do differ. The cause was 1 custom module with 1 file encoded in UTF-8, converting it to ANSI warnings are gone even without patch
Comment #39
shahidaali CreditAttribution: shahidaali commentedThe easiest way to find which module is producing error, just add
if(!isset($module->info['name'])) dpm($module->info);
inat the end of function
function system_modules($form, $form_state = array()) {
.This will tell you which module is producing error.
Comment #40
izmeez CreditAttribution: izmeez commentedPatch in comment #36 applies to drupal 7.78 without difficulty but does it really fix a problem or cover up some underlying issue such as an error in a module .info file or file encoding? It does not look like anything was committed to Drupal 8.