WordPress caught an error with one of your plugins, Braintree for WooCommerce P

Hey Mapal ( @mapallevy ),

Thank you for reaching out to us. Happy to help with your question!

This plugin is using our framework which we have developed for a number of our gateway plugins. In our framework there scripts we load in the front end, vs the scripts we load in admin. In many cases, these scripts will first check if the user is using an admin account to edit them, however, plugins like Elementor may not work well when editing checkout pages because they render the front-end of a page on the admin side, causing similar error.

In order to check if that’s the case, would it be possible to let me know if you’re encountering the same error with any other pages? Also, does the error persist when our plugin is disabled?

Looking forward to your response.

Best regards,
Pit

Hey Mapal,

It has been a long time since we heard from you, so I’m going to mark this topic as resolved. If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

Thanks,
Tamara ??

I am using Elementor with your Square for Woocommerce plugin. I have not edited the checkout page on my site (www.healingessencecbd.com) but continue to get this error message in Cleantalk Security:

“These files may not contain malicious code but they use very dangerous PHP functions and constructions! PHP developers don’t recommend to use it and it looks very suspicious.

/wp-content/plugins/woocommerce-square/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway-plugin.php
”
The problem does not persist if I deactivate the plugin.

Please advise.

Hi @chriscutler,

Thanks for reaching out. Happy to help you with this!

Although the SkyVerge gateway framework is still included in the WooCommerce Square plugin, we do not develop or support this plugin any longer. This will need to be addressed by the WooCommerce team directly, I’m afraid.

Please make sure to create a new topic on the WooCommerce Square forums so that one of their team members can take a look at this for you:
https://www.ads-software.com/support/plugin/woocommerce-square/#new-topic-0

Thanks,
Marcus

Hello,
I have the same issue as described in the original post by Mapal, which doesn’t seem to have been resolved here (the thread moves on to the WooCommerce Square plugin, which is a different matter).

Here’s the issue again: Elementor won’t load properly on the WooCommerce checkout page when the Braintree for WooCommerce Payment Gateway plugin is activated. Other pages are not affected, and the issue disappears when the plugin is deactivated. The error message is as follows:

Ein Fehler vom Typ E_ERROR wurde in der Zeile 766 der Datei
/srv/data/web/vhosts/www.nyanja.com/htdocs/wp-content/plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php
verursacht. Fehlermeldung: Uncaught Error: Call to a member
function render() on null in
/srv/data/web/vhosts/www.nyanja.com/htdocs/wp-content/plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php:766

Please can you advise?
Thanks,
Jonathan

Hi @jonathanlitscher,

Thanks for writing to us about Braintree for WooCommerce! I’m sorry to hear that the plugin isn’t working as expected. I am happy to help with this. ??

We’ve had a similar issue reported by other merchants that our engineers are working on patching up. In the meantime, we have a custom code snippet that should do what you’re looking for here, so I’m happy to share it! However, please be aware of a couple notes:

• I’m afraid that customizations are not covered under our support policy, so implementing this directly or modifying it further isn’t something we can assist with.
• Please be sure you know how to add custom code to your site. Personally, I like the free Code Snippets plugin method.

You can view the snippet here:
https://gist.github.com/e0eea9067a8861cbae61fa09626b7bd4#file-sv-wc-disable-gateways-for-elementor-editing-php

Would you please try adding that to the site and see if that allows you to then edit the checkout page with the Braintree plugin enabled?

Then, if you are still experiencing issues, per the forum guidelines, would you please make a new thread for continued support?

Thanks,
Benjamin

Hi Benjamin,
Thanks for the response, that worked.
Do I understand correctly however, that with this code all our payment gateways will be disabled whilst elementor is in editing mode, so we wouldn’t be able to receive any payments? In that case, I’d rather manually turn off the Braintree plugin only and leave the others on…
Do you have an indication on when the patched update will be available?
Best,
Jonathan

Hi @jonathanlitscher,

Great, so glad to hear it! ??

The snippet only disables the gateways for th editor, not for the site as a whole. So you should be able to see and edit the page with the editor without deactivating the gateways on the front of the site.

So even with the snippet active and the Elementor editor open, you should be able to receive payments from customers as usual.

As far as when the patch will be available, I’m afraid I don’t have an ETA as to when that will be complete. I’d recommend keeping an eye on the changelog for updates.

Does that give you the information you need?

Cheers,
Benjamin

Hi Benjamin,
Thanks a lot for clarifying, great to know we can have the code snippet in place without affecting the store front end.
That’s all I need in that case. Thanks again, really appreciate your support! ??
Cheers,
Jonathan

Hi @jonathanlitscher,

Great, glad to hear it! You’re very welcome ??

If you run into any further issues, please don’t hesitate to create a new thread – we’re happy to help.

Cheers,
Benjamin

We ran into the same issue. Reproduced it on multiple environments. The code snippet linked above (GitHub) does function as a workaround.

Still, this is a bug in the Skyverge plugin because that’s the source of the 500 error. No plugin should produce a 500 error under normal usage. It’s a bug for sure. There’s likely to be other avenues reproducing this vulnerability such as JS deferrals, which are becoming widespread these days, even part of the beta JetPack Boost plugin by Automattic.

This particular bug does exemplify problems with checkout previewing such as Elementor, but could very well apply the same to the new Woo Blocks Checkout and pretty much any builder for that matter.