Skip Navigation

[Resolved] woocommerce checkout fields are squashed

This support ticket is created 3 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 2 replies, has 2 voices.

Last updated by treyD 3 years, 10 months ago.

Assisted by: Minesh.

Author
Posts
#1649595
Screen Shot 2020-06-03 at 3.51.03 PM.png
Screen Shot 2020-06-03 at 3.49.55 PM.png

Hi, I have discovered that one of the Toolset suite of plugins is interfering with the display of Woocommerce checkout fields, and is squashing them all into a narrow column about 30px wide. I have verified this on three sites. I remediated the issue on one site by rolling back to previous versions, but on one site I can't do this, because I've built significant parts of the site using Blocks and Layouts in more recent Toolset version.

I've over-ridden the issue to some extend with CSS styles in the head, but the checkout fields are still not right.
I've attached screenshots of before applying and after applying the CSS below:

<style>.checkout .col-1,
.checkout .col-2 {
-webkit-flex: none;
-ms-flex: none;
flex: none;
max-width: none;
}
#payment li {
list-style: none;
}
</style>

#1649993

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

This is a known issue to us and you can check the further details and workaround with the following errata page:
=> https://toolset.com/errata/bootstrap-4-columns-classes-col-1-and-col-2-conflicts-with-woocommerce/

#1650751

My issue is resolved now. Thank you!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.