Conversation
supportI was previously getting error “Error: source_id – Field must not be blank” but after messing with some things, now I can make Square test payments, but the “thanks” screen doesn’t appear and no receipt email is sent out. Your plugin also seems to interfere with using the Test payment style of GiveWP. I click the submit button and nothing happens. The browser console shows the errors “Content Security Policy: The page’s settings blocked the loading of a resource at eval (“script-src”).” at iframe:112:30. I also see this warning: [Deprecated] On 07/15/2022, SqPaymentForm will be retired and functionality will no longer work. We encourage you to upgrade to the Web Payments SDK https://developer.squareup.com/docs/web-payments/overview So that’s happening soon! Is there a plan to deal with this? When I deactivate your plugin, the test payment mode of the form works fine. The thank you screen is displayed and a receipt email is sent. It’s your plugin that’s interfering with it, apparently. GiveWP by itself works fine. This topic was modified 4 years ago by Tyler Tork . The page I need help with: [ log in to see the link]
Hi @tylertork , Thanks for contacting us, I hope you are doing well, Please make sure that you have inserted the correct test Location id in the backend. Please see the screenshot . Thanks & Regards WP Experts Support Team
Yes, I have used the correct location ID. Even if it were incorrect, I’m not sure how that would cause a browser security violation. I also don’t know how that would affect the fact that you’re using an API that’s about to become defunct.
Hi @tylertork , We are aware of this and we will release an update before this API is deprecated. Thanks
Looks good, thanks!
Hi @tylertork , Thanks for contacting us, I hope you are doing well, Please make sure that you have inserted the correct test Location id in the backend. Please see the screenshot . Thanks & Regards WP Experts Support Team
Yes, I have used the correct location ID. Even if it were incorrect, I’m not sure how that would cause a browser security violation. I also don’t know how that would affect the fact that you’re using an API that’s about to become defunct.
Hi @tylertork , We are aware of this and we will release an update before this API is deprecated. Thanks
Looks good, thanks!