[Resolved] Conflicts with WooCommerce

[Author]

Posts

[serenus]

I seem to have resolved the original "look" issues by rebuilding from scratch in the new WordPress.
However, I am running into some conflicts with WooCommerce (e.g., billing fields layout - found the css fix). Are there known issues with WooCommerce besides css?
Is there an activation preference on multisites (i.e., network activate vs. individual site activate).
Sadly, I cannot use staging at my host because it is a multisite setup. It only available for single WordPress installs.

[Jamal]

Hello and thank you for contacting the Toolset support.

These are the known issues with WooCommerce:
- https://toolset.com/errata/woocommerce-blocks-loads-extra-google-fonts-files-on-the-front-end/
- https://toolset.com/errata/impossible-to-add-more-than-one-item-to-cart-on-the-shop-page-if-styled-with-woocommerce-views/
- https://toolset.com/errata/custom-size-attribute-on-wpv-woo-product-image-is-not-working-if-used-on-a-single-content-template/
- https://toolset.com/errata/when-using-translated-content-templates-for-woocommerce-products-woocommerce-styling-is-not-applied/
- https://toolset.com/errata/when-migrating-the-website-woocommerce-views-template-settings-are-lost/
- https://toolset.com/errata/pagination-displaying-twice-on-archives/
- https://toolset.com/errata/woocommerce-products-images-are-not-being-shown-if-they-are-added-in-a-views-slider/

If you are encountering another issue, please provide more details about it. What steps do you follow to see it? And, if possible, where can we see it on the frontend?

If you can't provide a staging site, let me see it on the live site, I won't change anything. Let me know if you want to share credentials, so I can activate a private reply for you.
I can also take a Duplicator copy to work on it locally or we can migrate it to our platform and work on it there.

[serenus]

Hi Jamal,

I just finished troubleshooting with Health Check. I was able to successfully activate all plugins on the theme (now the same child theme for main & sub). The moment I tried to activate ANY of the Toolset plugins, it broke things. The most obvious indication is a broken checkout form. I added some css for the billing section but not for the CC section. So it is to see that the fields are not usable and that's the clue 😉 They are perfectly fine without extra css when no Toolset plugin is active.
I am at a loss about what is going on and how to fix it. I think the underlying issue that caused the previous issues is still active and I can't identify it. I have a few PHP notices in debug but no errors.
I am happy to give whatever you need to figure this out.

[Jamal]

Please allow me temporary access to your website to check this further. Your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **

What do you mean by The moment I tried to activate ANY of the Toolset plugins, it broke things.?
Do you mean styles of the checkout page? Can you add a screenshot to explain further?

[Jamal]

I am sure you will understand that we, at the support team, work on different clients' websites and it became hard for us to keep track of each client's websites and contexts.

So, I am will need to have a concrete example of the issues with the tablepress shortcodes. Let me know what shortcodes? Where they are using? And preferably add screenshots from the frontend for both cases(broken, without Toolset plugins).

Regarding the issue with the CC fields, the only difference I spotted is the bootstrap styles files added by Toolset. If you deactivate loading the Bootstrap files the CC fields issues disappear. The setting is in Toolset->Settings->General(tab)->Bootstrap loading Check this screenshot hidden link
I am not sure if you are using Bootstrap styles on your website in other areas! If that's the case, we'll find a solution to fix the CC fields.
If you are not using Bootstrap across your website, just deactivate the loading for it in Toolset Settings. And maybe it will fix the tablepress shortcodes too.

Let me know if you need to load Bootstrap styles or not? If you rely on them in a content template, in Toolset forms, or somewhere else?

[serenus]

You ping pointed the main issue - bootstrap! I do use some bootstrap including in some Toolset content. It will take time to identify and replace all instances so I had decided to reactivate it in Toolset settings. It is on the to-do list to keep things cleaner and loading faster.

I added the following css code. It addresses ALL WooCommerce style issue instances.

.woocommerce-billing-fields .form-row, .woocommerce-shipping-fields .form-row,.woocommerce form .form-row {
display: block;
}
 
.woocommerce .col2-set .col-1, .woocommerce-page .col2-set .col-1,.woocommerce .col2-set .col-2, .woocommerce-page .col2-set .col-2 {
max-width: unset;
}

Right now, the Tablepress shortcodes are back to working. I am not quite sure why adding some css for WooCommerce would do that but... as long as it works correctly.

I have not troubleshooted all instances of shortcodes malfunctioning yet.

[Jamal]

Bootstrap is used for grids in the legacy views and if Toolset forms. If you are not using grids in your Forms, or if you are not using a grid layout in a legacy view you can safely drop Bootstrap.

[serenus]

Thanks for pointing this out. I will work towards that when time permits. I think MyCred also uses Bootstrap so there is quite a bit of digging to be done.
The struggle with porting this site to the new multisite structure was double-sworded - the new structure AND the ever-evolving WordPress ecosystem. It can be challenging to move older and larger websites along 😉
Thanks for your help, Jamal.