-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FOP_CreateFormOfPayment error: SOAP-ERROR: Encoding: object has no 'attributeType' property" #163
Comments
Can you get me the logfile of the entire request XML that is being sent? |
I've attached the log file. |
I can't see it right now, but there's probably a difference in the message version 11.1 (which you have in your WSDL) versus the 15.4 version I've used to implement the message. |
I think I may have found it. In version Maybe you can temporarily try to hack the file class GroupUsage
{
/**
* @var AttributeDetails
*/
public $attributeDetails;
/**
* GroupUsage constructor.
*
* @param string $fopType AttributeDetails::TYPE_*
*/
public function __construct($fopType)
{
$this->attributeDetails = new AttributeDetails($fopType);
}
} And after you do that, try to make the call again. If that fixes the problem, let me know here, and I'll make a fix to support both formats depending on the message version. |
Ok, the hack worked, but now I get this message: |
Did you update to version 1.6.1 of the library? I recently fixed that issue. |
Oh, My bad, I've updated and run again and it work perfectly. |
I'm going to keep this issue open as I want it to work with version 11.1 without having to hack that file. I'll close it when I've pushed that fix. |
Pushed a fix to the master branch to support You can test it by pointing your You should now be able to call this message using your 11.1 version without having to manually edit any files. Will be released with version 1.7.0. |
Version 1.7.0 has just been released! |
Hi,
I'm getting SOAP-ERROR when I try to add a credit car information to create an FP.
I just try using one of the examples in this page, and get the same error. I am wondering if this has something to do with the service version, I have in our WSDL Version 11.1.1A.
This is part of our code:
Thank you for your help
Ariel
The text was updated successfully, but these errors were encountered: