Undefined index: subclasses [#403426]

My log is full of notices like this:

[Mon Mar 16 12:29:11 2009] [error] [client 91.192.148.231] PHP Notice: Undefined index: subclasses in /home/cat/modules6/radioactivity/radioactivity.inc on line 99
[Mon Mar 16 12:29:11 2009] [error] [client 91.192.148.231] PHP Notice: Undefined index: subclasses in /home/cat/modules6/radioactivity/radioactivity.inc on line 124

Module works but this messages confusing me.

Comment	File	Size	Author
#8	undefined_index_subclasses-403426-8.patch	1.21 KB	ultimike
#8

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

skiminki CreditAttribution: skiminki commented 17 March 2009 at 07:26

In this case, those are harmless, really, but can bloat your logs. This happens because some is_set() calls are missing to suppress those warnings. Anyways, if you run production server, you should probably bump up your PHP log level into warning-level. I'm going to fix this before next release.

Comment #2

skiminki CreditAttribution: skiminki commented 17 March 2009 at 07:27

Actually, AFAICT, those aren't really even warnings but just notices.

Comment #3

greggles

he/him

English

Denver, Colorado, USA

CreditAttribution: greggles commented 17 January 2010 at 19:41

Status:

Active

» Postponed (maintainer needs more info)

They are just notices and ideally should be cleaned up as part of the coding standards about E_ALL code, but are not necessarily a priority.

I looked at the current code and it seems that these problems have been solved. Marking "needs more info" to see if anyone else is still seeing this problem.

Comment #4

skiminki CreditAttribution: skiminki commented 24 January 2010 at 19:41

Status:

Postponed (maintainer needs more info)

» Fixed

OK, found one more of these, fix committed. Marking this issue as fixed for now.

Comment #5

skiminki CreditAttribution: skiminki commented 24 January 2010 at 20:06

Still one more of these fixed and committed.

Comment #6

7 February 2010 at 20:10

Status:

Fixed

» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Comment #7

webkenny CreditAttribution: webkenny commented 11 October 2011 at 16:36

Version:	6.x-1.0	» 6.x-1.3
Status:	Closed (fixed)	» Active

Line 108 of radioactivity.inc - Looks like this issue still exists in some places. See the following which generates this error:

    // check if we need to resolve full classname
    if (is_array($decay_profile['energy'][$oclass]['subclasses'])) {
      foreach ($decay_profile['energy'][$oclass]['subclasses'] as $subsources) {
        if (isset($subsources[$source])) {
          // there is subclass specific energy value for the source, so
          // resolve subclass
          $classname=_radioactivity_resolve_classname($oid, $oclass);
          break;
        }
      }
    }