Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
node.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
25 Mar 2010 at 07:06 UTC
Updated:
2 Nov 2017 at 16:06 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedComment #2
dumbkid831 commented#1: 752486_1_admin_content_produces_php_warnings.patch queued for re-testing.
Comment #3
Stu-Druwser commentedDon't ask me how; but after applying this patch to my new D7 dev version I get these errors in my reports area and my site runs reaaalllll sloowwww. I get a lot of these, on every menu click.
Type cron
Date Friday, April 16, 2010 - 15:55
User Anonymous (not verified)
Location http://localhost/drupal-7.0/admin/reports?render=overlay
Referrer http://localhost/drupal-7.0/xxxxxxxxxx
Message Cron run exceeded the time limit and was aborted.
Severity warning
Hostname 127.0.0.1
Comment #4
Stu-Druwser commentedNever mind, http://drupal.org/node/453286 this was causing it.
Comment #5
JacobSingh commentedThis is a subtle logic change. not sure if it matters.
Here you say that if the language is not in $languages then $l_options should be array(). You assume that LANGUAGE_NONE will never be in $languages.
In this case, you are checking if it is not in $languages OR it is LANGUAGE_NONE. This assumes that LANGUAGE_NONE can be in $languages.
Which one is it?
I'm more curious why you are getting the notices, as in what is $node->language set to if not set to an existing language or LANGUAGE_NONE. perhaps it is not good to supres them? What if you import some nodes and the language they are set to doesn't exist in your system?
Comment #6
Anonymous (not verified) commentedI suppose allowing LANGUAGE_NONE would make more sense, if it appears in the array. At present though, I haven't really noticed this in quite a while. It might still occur, but I haven't seen it appear in the logs for a while. I'm not actually sure that it is still needed. Agree?
Comment #7
gábor hojtsyI would agree with Jacob that it is not a good idea to suppress these errors, since they indicate other errors in the system. If the $node is not an object as indicated above, then this is invoked with some bad arguments. If it uses a language code not defined that is another issue again. Since you don't experience this anymore, I think we can just close this out.