Thanks for the update @wpwench,
> My security plugin was loading an outdated PayPal JS file causing console/javascript errors like “paypal.Buttons is not a function”
Okay, that’s interesting and obviously not ideal that you need to deactivate a security plugin for this to work.
In v2.0.1 of PayPal Checkout we should have fixed all issues that were related to other plugins loading the legacy PayPal JS file (checkout.js).
It’s also not ideal that you are needing to disable this security plugin.
Do you have a staging/test site available to diagnose what is going wrong?
When you enable/activate this security plugin again, can you try to do a hard refresh of the webpage (i.e. command or ctrl + shift + R) and see if the problem still occurs.
Can you also send me a link to the page where you are seeing the problem so that I can take a look.
I would like to see what other PayPal JS files are being loaded. It’s possible there’s another conflict somewhere that we haven’t fixed yet.
> can you please elaborate
Yes, of course.
In v2.0.0, we stopped loading the old checkout.js
file in favour of upgrading our PayPal checkout integration to use the latest PayPal Javascript SDK (sdk/js
).
The new sdk/js
integration we wrote was using the global paypal
javascript variable to call new PayPal functions that didn’t exist in checkout.js
, namely paypal.Buttons, and paypal.getFundingSources.
So when there was another plugin loading checkout.js
it would could cause this problem with trying to call Paypal functions that don’t exist. We quickly resolved this issue and released it in 2.0.1: https://github.com/woocommerce/woocommerce-gateway-paypal-express-checkout/pull/740
Thanks
-
This reply was modified 4 years, 10 months ago by
mattdallan.