Closed jacoswan closed 9 months ago
Thanks @jacoswan for the detailed report!
I've tested with the latest develop
branch, and confirmed the issue with some notes:
To Reproduce
section above, then reloading the full checkout page and choosing Use a new payment method
, the card fields are rendered properly.Noting this needs testing against the new dUPE to test if this is still reproducable.
This issue impacts accounts domain, so assigning to Heisenberg (based on team responsibilities Pc2DNy-3z-p2) @FangedParakeet. . Assigning as part of Gamma Triage process PcreKM-yM-p2.
I just verified the behavior, and the issue doesn't seem to be present anymore. It might have been affecting older versions of the Payment Element. Here's a screencap of the current behavior. I ensured that a similar setup was done (free product w/ free shipping, and addition of new product requiring a payment method).
Describe the bug
Not sure if a Payments bug or Order Bump bug (hence
type: question
). Starting here (have pinged Order Bump devs for a look too).When starting off with a free product, then adding a product on the checkout page via Order Bump for WooCommerce, the Use a New Payment Method option doesn't render the credit card fields.
To Reproduce
Actual behavior
Credit card fields are not rendered when starting from a free product, the order is bumped to includ a paid product.
Screenshots
Expected behavior
Expected the credit card fields to render, especially when new payment method is selected. It does render if a paid product is in the cart, or in the cart together with the free product. Using a gateway with similar features, such as Stripe, also works as expected.
Desktop (please complete the following information):
Additional context
Reported in 4907820-zen
Pressable site: Jetpack | | by Automattic – 10.8-beta Order Bump for WooCommerce by FantasticPlugins – 2.0 WooCommerce Payments by Automattic – 3.9.1 WooCommerce by Automattic – 6.3.1