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 |
Comments
Comment #1
skiminki commentedIn 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 commentedActually, AFAICT, those aren't really even warnings but just notices.
Comment #3
gregglesThey 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 commentedOK, found one more of these, fix committed. Marking this issue as fixed for now.
Comment #5
skiminki commentedStill one more of these fixed and committed.
Comment #7
webkenny commentedLine 108 of radioactivity.inc - Looks like this issue still exists in some places. See the following which generates this error:
Comment #8
ultimikeAttached is a patch to check for the existence of subclasses before they are accessed (see comment 7 above).
Thanks,
-mike
Comment #9
the_g_bomb commentedConfirmed this patch works and clears up the errors.
Comment #10
sutharsan commentedIssue triage: Closing issue, the 6.x branch is no longer maintained.
If you believe this issue is closed in error, feel free to re-open.