-
Notifications
You must be signed in to change notification settings - Fork 220
Update wording on checkout error message to try to prevent retries #10888
Conversation
The release ZIP for this PR is accessible via:
Script Dependencies ReportThere is no changed script dependency between this branch and trunk. This comment was automatically generated by the TypeScript Errors Report
🎉 🎉 This PR does not introduce new TS errors. |
Size Change: +253 B (0%) Total Size: 1.47 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚀
@opr are we sure the email is sent at this point if the order is placed? |
@ralucaStan We're not sure that the email has been sent at this point, that's the issue. The fail could have happened at any point in the checkout process, so we don't know if the order was successful or not, the idea of this PR is to get the user to double check if the order placed before retrying to prevent double orders.
Yes, actually we could, if the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've adjusted the messages. curious to hear what you think
@@ -293,12 +295,20 @@ const CheckoutProcessor = () => { | |||
__internalProcessCheckoutResponse( response ); | |||
} ); | |||
} catch { | |||
let errorMessage = __( | |||
'Something went wrong, but your order may still have been placed. Please check your email inbox before retrying.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something went wrong when placing the order. Check your email for order updates before retrying.
|
||
if ( customerId !== 0 ) { | ||
errorMessage = __( | ||
'Something went wrong, but your order may still have been placed. Please check your email inbox or your order history in the "My Account" area before retrying.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something went wrong when placing the order. Check your account's order history for order updates before retrying.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should still include email here, but otherwise fine. Let me update them.
8a93992
to
ffdd46c
Compare
Bumping the PR to the next release |
This PR has been marked as If deemed still relevant, the pr can be kept active by ensuring it's up to date with the main branch and removing the stale label. |
Bumping PR to next release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not realise this wasn't approved. Approved, thank you for the patience
What
This PR updates the error message on the Checkout block that's displayed if an error is encountered during processing. It recommends the user checks their email or My Account area before retrying to prevent duplicate orders.
Partially solves woocommerce/woocommerce#42223, however we will keep that open until a more robust solution is in place.
Why
Some shoppers would continually retry their order when seeing this error as it's unclear that the order was placed.
Testing Instructions
Please consider any edge cases this change may have, and also other areas of the product this may impact.
Screenshots or screencast
WooCommerce Visibility
Required:
Checklist
Required:
[type]
label or a[skip-changelog]
label.Conditional:
[skip-changelog]
label is not present).Changelog