SOLVED: Place Order button on Checkout doesn't work when Stripe switched to New Checkout

Bugs
1

Browser: Chrome 110 / Firefox
OS: Windows
Video: Jam

Place Order button on Checkout doesn’t work when Stripe switched to New Checkout.

When I disable the Legacy Mode in Stripe Settings the Place Order button doesn’t do anything.

When switched to 2025 theme, everything works fine.

You can see that on my screen recording.

I have experienced the same issue in both Normal and Test Mode of Stripe.

I can replicate the issue on different browsers.

I have tried switching all the plugins off, aside from WooCommerce and Stripe, and while Bricks Theme is active the issue persists.

The moment the theme is switched to either 2024 or 2025, Checkout with Stripe Legacy Mode disabled works fine.

Please let me know if you need any more details or access to the staging site.

Thanks
Matt

2

Hi @matt-cnc ,

Can you check if you have setup the Checkout template properly?

If you edited the Checkout page with Bricks:

  • Ensure [woocommerce_checkout] shortcode is in the Bricks data

If you didn’t edit the Checkout page with Bricks:

  • Ensure [woocommerce_checkout] shortcode in the Gutenberg content.

If it’s still not working, please send your admin credentials to help@bricksbuilder.io and include this thread URL as a reference. Please use your license-purchased email when composing the email so we can verify license ownership.

Regards,
Jenn

3

Hi @itchycode ,

The template is setup correctly, the checkout is working currently on the live/production website, while Stripe is in legacy mode.

I have sent you access details to the staging environment, on which we can reproduce the issue, as shown on the screen cast.

Waiting for your response.

Thanks,
Matt

4

Hi @matt-cnc

Thanks for the login details.

Found that it’s a bug on the Checkout Customer Details element when removing billing/shipping fields.

image

Recorded in the bug tracker.

Regards,
Jenn

2 Likes
5

Thank you, @itchycode !

Looking forward to an update when this gets fixed with the next release.

Thanks,
Matt

6

Hi @matt-cnc ,

We’ve fixed this in Bricks 1.12 BETA, now available as a manual download (Bricks – Account)

Please let us know if you are still experiencing issues.

You can see the full changelog here: Bricks 1.12 Changelog – Bricks

As with any beta release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.

Best regards,
Matej

1 Like