0

I could need some help.

I've added a custom payment method to our shop following this tutorial: https://webkul.com/blog/create-custom-payment-method-magento2/

So far so good, but after loading the checkout page we get the following error:

Uncaught ReferenceError: Unable to process binding "if: function(){return quoteIsVirtual == 0 }" Message: Unable to process binding "if: function(){return isIncludingDisplayed() }" Message: Unable to process binding "if: function(){return haveToShowCoupon() }" Message: haveToShowCoupon is not defined at if (eval at createBindingsStringEvaluator (eval at require.load (b1654aa9974d62289672a4f5a5a23090.min.js:1)), <anonymous>:3:55) at ko.computed.disposeWhenNodeIsRemoved (eval at require.load (b1654aa9974d62289672a4f5a5a23090.min.js:1), <anonymous>:373:702) at Function.evaluateImmediate_CallReadThenEndDependencyDetection (eval at require.load (b1654aa9974d62289672a4f5a5a23090.min.js:1), <anonymous>:205:240)

Here is a simmilar problem: Uncaught ReferenceError: Unable to process binding "if: function(){return isExcludingDisplayed() }" After Magento 2.3.4 Upgrade Checkout Cart Page

The thing is i have'nt altered the shipping.js files. And when i remove the payment method, the checkout is back in his normal state.

Does someone have an idea what file could have such an impact? Or where i could look to fix it? Or if you need more information, ask. I'll try to give you as many as possible.

Thanks in Advance!

Improve this question

1 Answer 1

Reset to default
0

It's hard to answer without seeing all your code but I suspect this error means there is a KO binding in a template that does not exist in the Javascript. Try searching all HTML files for quoteIsVirtual == 0 and hopefully you will find some results and can debug from there.

So fix this find the JS component for that template and ensure the data you're using in the template is accessible.

Improve this answer
2
  • hrrrr, i feel so stupid. We have a custom Theme running where we had the shipping.js copied. And we have'nt copied the changes from 2.3.3 to 2.3.4 memo to me: double check for local changes Commented Oct 28, 2020 at 16:07
  • Haha this happens with every damned upgrade, it's painful but it's at least it's resolved! Commented Oct 29, 2020 at 8:57

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.