I get the error message "Notice: Undefined index: name in system_requirements() (line 40 of /mypath/modules/system/system.install)." on the Status Report page. I found an issue addressing this, but it seemed to be for an old dev version and about the message reporting, not that it was thrown. Thoughts?

Comments

Starminder’s picture

I'm getting the same error :/

jkaine’s picture

Didn't get it until I migrated my D7 site from one server to another.

mibfire’s picture

+1

nelsinchi’s picture

I have also the same message error. Please anyone could fix this problem??? I just updated from Drupal 7.0 to 7.2.
Thanks

toma’s picture

I just updated from Drupal 7.0 to 7.2 when i get this message

Modules installed
Views 7.x-3.0-beta3
Views exporter 7.x-3.0-beta3
Views Slideshow 7.x-3.0-alpha1
Views Slideshow: Cycle 7.x-3.0-alpha1

Another error message

Notice : Undefined index: distribution_name dans drupal_install_profile_distribution_name() (ligne 202 dans /home/icifranc/public_html/includes/install.inc).

ckrina’s picture

I've uptated from Drupal 7.0 to Drupal 7.2 too, and have this errors:

In /modules:
"Notice: Undefined index: distribution_name a drupal_install_profile_distribution_name() (línia 202 de /Applications/XAMPP/xamppfiles/htdocs/includes/install.inc) "

In /Configuration:
"Notice: Undefined index: name a system_requirements() (línia 39 de /Applications/XAMPP/xamppfiles/htdocs/modules/system/system.install)."
"Notice: Undefined index: version a system_requirements() (línia 41 de /Applications/XAMPP/xamppfiles/htdocs/modules/system/system.install)."

Thanks!!!

ckrina’s picture

Take a look here: it fixed the problem for me.
http://drupal.org/node/679730#comment-4529410

sakib000’s picture

I also had same error after upgrading a drupal 6 site (which was initially installed using installation profile) to Drupal 7.12. After i explored the database, i found following responsible table:

system/profile

i changed status of initial installation profile to '0'
and changed status of currently active install profile to '1'

that fixed m issue.

Mohd Sakib
http://www.worthapost.com/
Email: sakib.live [at] gmail.com

scottshipman’s picture

What do you mean by table system/profile.

I have a system table, with records relative to the profile module from core.

I am running 7.15. I originally installed the Acquia profile, but then deleted the profile folders and embedded modules.

rasor’s picture

Ditto - I also would like to know. I suppose it is a D6 table.

I have a 7.14 updated to 7.15.
The 7.14 is initially installed using "Localized Drupal Distribution": http://drupal.org/project/l10n_install
I have a table called l10n_update_project containing a row having core version still set to 7.14. It did not help to update that to 7.15.

BTW - there is a patch here: http://drupal.org/node/679730#comment-4529410. I haven't installed it, so I don't know if that solves it.

cumpatomas’s picture

I've solved it following this instructions:
http://www.drupaldeveloper.es/en/notice-undefined-index-name-in-system-requirements-linea-39-y-41

Be sure of:

1-Make a back up of the original file
2-Copy and replace the whole part of the code with all the symbols shown

I don't know much of programming so I really don't know what are the changes made.

cheers!

ibevamp’s picture

yep. That worked for me.

CybrRob’s picture

That worked perfectly for me too. Thanks.

ASP.Net/C#/VB/SharePoint/Drupal Developer

webdrips’s picture

This worked thanks

Need Drupal module or theme design? Please visit Webdrips to learn how we can help.

Nora McDougall’s picture

Yes, it worked to solve my second upgrade issue very handily! Thanks a bunch for the link!!!

So, back to the first issue on the Modules page ... (see next comment)

kaldimar’s picture

I started getting this error after moving a site from Aegir to Rackspace. The link provided by cumpatomas helped me to solve the issue in minutes. Thank you!

gianfrasoft’s picture

The patch solved my issue!!!

Thank you!

Web Software Engineer at
Insem S.p.A. - www.insem.it

ethompsy’s picture

Try this fix first. So easy. Do save a copy of your file first.

Nora McDougall’s picture

Our install was originally done with Kickstart. We upgraded once without problem. Now the upgrade to 7.19 is producing the same error discussed here and an error that only shows up on the Modules page: Undefined index: distribution_name in drupal_install_profile_distribution_name() (line 207 of /.../.../includes/install.inc). These errors may or may not be related.

Nora McDougall’s picture

For those of you who feel like you are "lost in translation" and who may make errors because of it, here is my experience.

Back up your database before you play with this stuff.

Based on my review of 3 pages of comments and folks with similar problems, these two errors are indeed related, and they are common. One solution mentioned in many comments is to change a status from 0 to 1. As near as I can interpret from the Drupal-speak, the problem lies in the systems table in the record with the first 0 being the status field:

profile module 0 0 -1 0 a:13:{s:4:"name";s:7:"Profile";s:11:"description";s:36:"Supports configurable user profiles.";s:7:"package";s:4:"Core";s:7:"version";s:4:"7.19";s:4:"core";s:3:"7.x";s:5:"files";a:1:{i:0;s:12:"profile.test";}s:9:"configure";s:27:"admin/config/people/profile";s:6:"hidden";b:1;s:7:"project";s:6:"drupal";s:9:"datestamp";s:10:"1358374870";s:12:"dependencies";a:0:{}s:3:"php";s:5:"5.2.4";s:9:"bootstrap";i:0;}

However, this also does not seem to be the correct record because admin/config/people/profile does not seem like a reference to an install profile. But, that is the only record in the systems table that has profile in the first field. So, for kicks and giggles, I went ahead and changed the 0 to 1 in this record. Everything seemed to be unchanged until I cleared the cache and the resulting page is only an error: Additional uncaught exception thrown while handling exception.

mvinas’s picture

my instalation was installed with a custom profile called "custom" (custom.profile). I noted that this module had a wrong status in the system table , I simply updated it using the following SQL:

UPDATE system SET status = 1 where name = "custom";

After clean all caches the error messages dissapeared.

I hope this will be useful.

Anybody’s picture

I can confirm that this worked great!
It seems that there is a problem with old install profiles.

Solution as described above:
Search for the name of your install profile (can be found in the "Status Report", Second line of the table) in the DB "system"-table and set status to "1" for it!

http://www.DROWL.de || Professionelle Drupal Lösungen aus Ostwestfalen-Lippe (OWL)
http://www.webks.de || webks: websolutions kept simple - Webbasierte Lösungen die einfach überzeugen!
http://www.drupal-theming.com || Individuelle Responsive Themes

labboy0276’s picture

I can confirm this works,

Look at your Status Report for the profile name, open up your DB (drush sql-cli or whatever)

UPDATE system SET status = 1 where name = "what ever your profile name is";

thanks for this one and you don't need to hack core, which is a very bad practice.

acbramley’s picture

This can happen after installing drupal using the minimal installation profile, simply setting the variable "install_profile" to "standard" will stop these errors as drupal will stop scanning for an info file.

drush vset install_profile "standard"

coolhandlukek2’s picture

subscribe

SchnWalter’s picture

--
Walter S.

bradallenfisher’s picture

this solved it!

bacteriaman’s picture

drush vset install_profile "standard"

Worked for me too--thanks.

stephit’s picture

Just FYI for anyone who might be helped by this module - I made the mistake of removing an installation profile and was getting the error message. This Profile Switcher module allowed me to switch to the standard install profile and fixed the error:

https://drupal.org/project/profile_switcher

JCB’s picture

I can confirm that Profile Switcher Module solved my problem.

izus’s picture

i had this issue installing Drupal 8, to solve it juste add the following to settings.php file (and adapt it to your installed profile)

<?php
$settings
['install_profile'] = 'standard';
?>

Twitter: @ismaeil_

zwerg’s picture

That doesn't work for Drupal 7.34 (same issue after update 7.32 -> 7.34).

And if you change your settings.php file you can't use the <?php ?> tags.

bacteriaman’s picture

Use of php tags in snippets is for illustration purposes only. FYI