Closed (fixed)
Project:
Drupal core
Version:
x.y.z
Component:
menu system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Sep 2005 at 14:38 UTC
Updated:
18 Sep 2005 at 17:03 UTC
Jump to comment: Most recent file
Comments
Comment #1
m3avrck commentedConfirmed error on PHP5 here. Patch does indeed fix problem, which not only creates the warning, but prevents rest of page from showing since output occured before the headers were sent.
Comment #2
killes@www.drop.org commentedI think this error was caused by a callback argument in comment.module that was a string. this has been fixed a few days ago. So I think we won't need this patch. Can somebody confirm this?
Comment #3
killes@www.drop.org commentedOk, I've been convinced that this is nto the same error. In fact, there is no callback arguement set and that is why it errors out. Please commit.
Comment #4
ax commentedan alternative patch that goes to the root of the problem (i think) and prevents that empty array wrongly to be set at the first place. there is no 'callback arguments' key in the 'comment/reply' menu item, so it shoudn't be set (to NULL) neither (to not fool later array_key_exists() checks).
please consider this instead.
Comment #5
ax commentedto be completely sure, there probably should be similar
isset()checks around both ofas both keys aren't required in menu items (according to drupaldocs.org).
Comment #6
moshe weitzman commentedax's brief patch looks good to me. a few days ago, i tried to track this down for a while but failed. nice work thox and ax.
Comment #7
m3avrck commentedTested and confirmed, patch works on PHP5, great find ax!
Comment #8
killes@www.drop.org commentedCorrect, ax' patch is the better one, eliminating the root cause.
Comment #9
Thox commentedYep, +1 on ax's patch. I'm glad someone understands the menu system ;)
Comment #10
dries commentedCommitted to HEAD. Thanks.
Comment #11
(not verified) commented