Open bastienho opened 1 year ago
Thanks for reporting @bastienho.
We currently have any client actively using this extension, would you be able to propose a fix?
would you be able to propose a fix?
Oh, sorry, I think you did: #20
Shoud I release a 1.2.0
version?
Nothing more for me. Fill free to release.
Thanks
@bastienho I tagged a 1.2-alpha1
version, see attachment. Could please test well and confirm that everything works?
Everything sounds good to me.
Thank you for the quick merge.
Ok, I'll ask you again in a week or so, and then create a release.
Not sure to understand you last comment. I've tested the 1.2-alpha1 and it worked well.
Not sure to understand you last comment. I've tested the 1.2-alpha1 and it worked well.
I mean a "proper" 1.2.0
release, no alpha/beta
Is this issue related to https://github.com/Project60/org.project60.sepapp/issues/17 ?
Is this issue related to #17 ?
Possibly. As I mentioned, I don't currently actively work with this extension, so I have no up-to-date information.
I just figured an unexpected behavior : when editing some non SEPA payment processor, an exception occurs:
Exception: "Couldn't find PaymentProcessorType [xxx]"
It seems to be related to the bad syntax (=
instead of ==
) in:
($pp['class_name'] = "Payment_SDD" || $pp['class_name'] == 'Payment_SDDNG')
Since CiviCRM 5.61, update or creation of PaymentProcessors always crash with this message:
After investigation, it occurs in these lines of
sepapp_civicrm_postProcess()
:If checked-up the exception, and the message return by
$ex->getMessage()
is:In fact, there is a breaking change on Contribution CiviCRM 5.61, particulary, this PR.
The
name
attribute is no more passed, the the PaymentProcessor can't be fetched.