Closed (won't fix)
Project:
Services
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Dec 2009 at 14:09 UTC
Updated:
29 Jul 2011 at 21:59 UTC
Jump to comment: Most recent file
Comments
Comment #1
greg.harveyMoving over to now active dev branch.
Comment #2
skyredwangif Drupal-user-logout returns a boolean value, then Services just pass the value to the server. In this case XMLRPC, if the specification of XMLRPC requires an array value, then it might be the server's responsibility to ensure that.
Comment #3
gddSo in theory skyred is right, we're not doing anything different here than anywhere else, and tracing through the call stack I don't see anything untowards. However I did notice that in the method signature for user.logout, it lists the return value as struct when we are returning a bool. I could see this causing errors up the way. Greg can you try changing that to bool and see if it fixes your problem? Note this is kind of just a shot in the dark that seems to make sense from looking at the code.
Comment #4
gddI committed the attached patch today, if you continue having issues please reopen.
Comment #5
greg.harveyHi, sorry I didn't find time to test this. Thanks for posting the patch. I have a test script that will expose if this is still a problem - at some point I'll download the latest snapshot and see, but you probably fixed it. =)
Comment #7
greg.harveyUsing the latest release, which was packaged after this patch, and the problem persists:
Comment #8
greg.harveyUpdating title, following on from skyred's comments.
Comment #9
marcingy commentedbumping version
Comment #10
kylebrowning commentedunless someone provides me with PHP to show this error happening or a test, or gives a patch that fixes this (WITHOUT CHANGING A RESOURCE), I'm marking this as won't fix.