SOAP-ERROR: Encoding: string 'Bo [sDetails] => getMerchant

[authcode]

soaperror Object ( [sCode] => SOAP-ENV:Server [sString] => SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string <...>
'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'SOAP-ERROR: Encoding: string 'Bo [sDetails] => getMerchant: )

1


Warning: Invalid argument supplied for foreach() in ......./includes/classes/class.api_merchant.php on line 67

Can't figure out if this one's me or a problem with the data that's getting returned? Anyone had a similar problem?

[Jon]

I've noticed similiar responses when working with the raw soap messages, make sure the values you are supplying a) are the correct type i.e string, int etc b) the value exists in the shopwindow DB

An example...

If I set aMerchantId to a value that is not a valid merchant id then the response comes back SOAP-ERROR: Encoding string - etc etc

Hope that helps...

[authcode]

Thanks FreeContribute. Haven't come across this error before and don't remember changing anything but I'll check through my code again and see where I might be going wrong. Thanks for the help.

[authcode]

I started printing debug info to screen to try to nail this bug. I was requesting 25 merchant objects via getMerchant drawn from 25 random hotpicks for all categories. The debug info confirmed that all of the merchant ids I was passing were valid (I checked them against the merchant manager spreadsheet and all were present and active). Then I created a spreadsheet consisting of the list of 25 merchant ids every time the bug occured. After 10 bad requests I checked the 10 columns for a pattern and merchant 1474 appeared every time. After blocking merchant 1474 via the control panel I have not had a repeat of the above bug.

It would appear a request via getMerchant for merchant 1474 is returning bad data. Please could someone from AW confirm this?