Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
10 Jan 2008 at 00:21 UTC
Updated:
12 Mar 2010 at 08:02 UTC
Jump to comment: Most recent file
When a call is successfully excuted via xmlrpc a notice is generated
Trying to get property of non-object in C:\broker6\includes\xmlrpcs.inc on line 70.
Patch to remove notice
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 208195-xmlrpc-notice.patch | 647 bytes | boombatower |
| #1 | xmlrpcerrjv.patch | 696 bytes | jvandyk |
| xmlrpcs.inc_.patch | 602 bytes | marcingy |
Comments
Comment #1
jvandyk commentedWe should check if it's an object. If it's not an object, it's not an xmlrpc error object and we shouldn't be looking for a property on it.
Comment #2
boombatower commentedThis is extremely annoying when working with XML-RPC as I do with PIFR/PIFT. Every time any traffic goes through I get those messages in my watchdog log. I submitted the patch that fixed this in D7, lets get this in.
Comment #3
dave reidBy the way, you can (and should) roll all that into
!empty($result->is_error).Comment #4
boombatower commentedSeems to work locally.
Comment #5
dave reidAlmost there... empty($result->is_error) should also cover the condition is_object($result). :)
Comment #6
dave reidSo crazy result, it will only return true if
$result = array('is_error' => TRUE);. So I guess checking is_object is fine too.Comment #7
boombatower commentedping.
Comment #8
gábor hojtsyThanks, committed to Drupal 6.
Comment #10
mr.baileysIssue for D7: #677750: XMLRPC server call creates unnecessary watchdog entries