WordPress.org

Resolved paulcxl
(@paulcxl)

6 months, 3 weeks ago

UX flaw here is that once customer returns from PayPal environment to the checkout page, form gets automatically submitted, resulting in T&C error because the checkbox is ought to be checked after (see screenshot, this is default WC setup).

Is it possible to prevent auto-submit after return from PayPal and have the user click “Place order” CTA instead to submit the checkout form?

—

And confirming once more, this is default plugin behavior, no other 3rd party plugin is overriding anything.

The page I need help with: [log in to see the link]

Viewing 14 replies - 1 through 14 (of 14 total)

Afzal (woo-hc)
(@afzalpansuvi)

6 months, 3 weeks ago
Hi @paulcxl,

Thank you for contacting WooCommerce Plugin Support. I understand that you are experiencing a UX flaw with the PayPal submit feature. The link you have shared for the page you need help with is not a valid link. Please provide us with a working link to your site so that we can inspect the issue further.

In the meantime, you can try to disable the auto-return for website payments option in your PayPal account settings. This option may cause the form to be submitted automatically before the customer can check the T&C checkbox. To disable this option, please follow the steps below:
- Access your PayPal dashboard, then navigate to Account Settings -> Website payments.
- Tap the Update link next to the Website preferences option.
- Enable the Auto return for website payments, then add your store’s thank you page link in the Return URL field.
- Save the changes.
We hope this helps you resolve the issue. If you have any further questions or concerns, please feel free to reply to this thread.

Thank you for choosing WooCommerce and have a great day!
Thread Starter paulcxl
(@paulcxl)

6 months, 3 weeks ago
Thank you for your reply!

My URL was supposed to represent all WC sites with this plugin installed, sorry if it didn’t come off that way (http://All%20WC%20sites%20with%20this%20plugin%20installed). Our company URL is https://cxl.com/.

The “auto-return” setting is already disabled from our side, so unfortunately it’s not that but something in the plugin itself that triggers a submit on WC side.
- This reply was modified 6 months, 3 weeks ago by paulcxl.
- This reply was modified 6 months, 3 weeks ago by paulcxl.
anastas10s
(@anastas10s)

6 months, 3 weeks ago

Hi there @paulcxl 👋

Thank you for reaching back, with further details on this.

The “auto-return” setting is already disabled from our side, so unfortunately it’s not that but something in the plugin itself that triggers a submit on WC side.

From what I gather, the screenshot showcases a WordPress Multisite being used.

To clarify, did you already have a chance to test with a standalone installation, and either the shortcode or block-based Checkout page layout, and see if the issue persists, or otherwise?

Looking forward to hearing from you!
Thread Starter paulcxl
(@paulcxl)

6 months, 3 weeks ago
Hey!

To clarify, did you already have a chance to test with a standalone installation, and either the shortcode or block-based Checkout page layout, and see if the issue persists, or otherwise?

The storefront staging site has a clean up to date WC installation with no 3rd party plugins interfering its functionalities. The URL we tested it on is different from our production site (cxl.com) which is not multisite, but same issue occurs there also.

And for the second part of your question, we’re currently using `woocommerce_checkout´ shortcode to load the checkout form.
- This reply was modified 6 months, 3 weeks ago by paulcxl.
lkraav
(@lkraav)

6 months, 3 weeks ago
We’d like to investigate assets/js/frontend/wc-braintree.js for details – it’s highly likely about avoiding submit in on_approve() execution, but surprisingly plugin doesn’t ship with unminified source at https://plugins.trac.wordpress.org/browser/woocommerce-gateway-paypal-powered-by-braintree/tags/3.1.1

Most other plugins ship with unminified sources, so core SCRIPT_DEBUG constant can do its job. Would you consider changing your release build process to accommodate SCRIPT_DEBUG for the next release? In the meanwhile, we’d appreciate if you could share an unminified copy as a gist, or whatever equivalent, tyvm!
- This reply was modified 6 months, 3 weeks ago by lkraav.
Plugin Support Zubair Zahid (woo-hc)
(@doublezed2)

6 months, 2 weeks ago
Hello paulcxl

Thank you for your reply.

Since you have a set up Staging site separately from your production site it would be very helpful if you could provide the following details of that site:
1. System Status Report: Navigate to WooCommerce > Status on your admin dashboard. There, select “Get system report” and then “Copy for support”. You can paste the report in your response here.
2. Error Log: Share a copy of the fatal error log. You can find this under WooCommerce > System Status > Logs.
With this information, I will be better able to investigate and understand what might be causing this issue on your site.

Looking forward to your response. 🙂
lkraav
(@lkraav)

6 months, 2 weeks ago

Please find out about providing proper JS source code access, and let us know.

Plugin Support Sean O))) a11n
(@seanomattic)

6 months, 2 weeks ago

Hey @lkraav,

To confirm, are you using this PayPal Braintree extension?

If so, please head to woo.com/support, open a ticket and reference this forum thread.

Thanks!

lkraav
(@lkraav)

6 months, 2 weeks ago

To confirm, are you using this PayPal Braintree extension?

Yes, it’s this extension, we’re in the right place. OK we’ll take it to woo.com.

Plugin Support Sean O))) a11n
(@seanomattic)

6 months, 2 weeks ago

Great! Pop your ticket number here as well, so we don’t miss you!

lkraav
(@lkraav)

6 months, 2 weeks ago

Ticket #7606622

Plugin Support carolm29 (woo-hc)
(@carolm29)

6 months, 2 weeks ago

Hey, @lkraav!

Thanks for sharing the ticket number.

I see we already followed up with you there, so I’m going to mark this as resolved as we continue to help you on the ticket, okay?

Have a wonderful day!

lkraav
(@lkraav)

6 months, 2 weeks ago

Well, there are certainly more developers who would like to know why this plugin doesn’t respect WP core standard SCRIPT_DEBUG constant and ship unminified JS assets so customers development teams could do their job better. In that sense I’d like to leave it open until we have a response.
Plugin Support Feten L. a11n
(@fetenlakhal)

6 months, 2 weeks ago
Hi there!

Thank you for your answer.

Yes, sure, we can leave this topic open; Please note that if someone uses the PayPal Braintree extension, they can contact us from woo.com/support.

Have a nice day!
- This reply was modified 6 months, 2 weeks ago by Feten L. a11n.