Checkout Manager form-row-first, etc. always gets overwritten?

Support
#1

Hi,

we are trying to use the Checkout Manager extension to make more fields in two rows using form-row-first and form-row-last classes. But somehow it always gets overwritten on the frontend. I already tried to disable all third party plugins except WooCommerce and Checkout Manager and also tried to use the Pro Theme without the child theme and it’s custom css – always the same.

Please put something in the cart and proceed to checkout to see the behavior for yourself. For a brief millisecond the two rows can be seen and then they get back to full width.

#2

Hi Alex,

Thanks for reaching out.

We can’t determine which one in the checkout page you are referring to. I would suggest that you provide us a screenshot of what items you are referring to in the checkout so that we can better help you with your concern.

Hope that helps and let us know.

Thank you.

#3

These two are configured to show in two rows:

Bildschirmfoto 2020-12-04 um 15.16.28
Bildschirmfoto 2020-12-04 um 15.16.282540×756 29.9 KB

#4

Hi Alex,

I just check the CSS class name of that two fields Straße und Hausnummer and Hausnummer. The reason why they didn’t go into two columns because there’s no form-row-first class name in the Straße und Hausnummer field. If you can change the class of Straße und Hausnummer from form-row-wide to form-row-first then it will fix the issue.

image
image1003×471 71.7 KB

Hope that helps.

Thank you.

#5

Sadly that’s what is the problem here: They already have “form-row-first” and “form-row-last” attached, also “Straße und Hausnummer” is called “Straße” but on frontend there’s still “Straße und Hausnummer” as title. So except for adding a new field everything else in Checkout Manager is overwritten by something in theme. I’ve added you a admin account, so you may can check for yourself?

#6

Hey Alex,

I could replicate the issue. Billing 1 reverts to the WooCommerce original setup,

The solution for this is to use Custom Fields instead of editing built-in WooCommerce fields.

I’ll post this as a bug in our issue tracker so this will be queued for fixing.

Thanks.

#7

Ok, thanks!

#8

You’re welcome and thank you for understanding.

#10

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.