Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.There is a PHP error in abuse_coment() function that leads to a PHP fatal error. The $comment variable is used as an array while it is an stdClass object.
The attached patch fix this.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | abuse_objasarray.patch | 563 bytes | bluetegu |
| abuse.module.patch | 596 bytes | claudiu.cristea |
Comments
Comment #1
bluetegu commentedHi Claudiu, I got this error too. However I think the root of the problem is a missing break statement. Per the api, hook_comment first parameter is an array when the op=update. Attached is a proposed patch. Feedback appreciated.
Comment #2
nancydruI have the patch from #1 applied and still get
Comment #3
nancydruClaudiu's original patch seems to solve this.
Comment #4
nancydruI suspect that both patches are needed.
Comment #5
bluetegu commentedHi Nancy,
Its great to get immediate feedback!
The received the error (warning) when I deleted a comment. Once I added a break statement the warning went away, and this is rather obvious from the code.
I tried to update a comment to see whether I can reproduce the error on update comment operation, without applying Claudiu's patch, and I didn't get any error or warning. I verified that indeed the abuse_comment function was called by printing to the screen. So bottom line, I can't reconstruct the problem you are having. I'm reluctant to apply Claudiu's patch without further understanding reasons/scenarios.
Best,
Bluetegu
Comment #6
nancydruClaudiu's patch is pretty obvious to me. It changes array references to object references. Once I applied it, my problem went away immediately.