OK, I finally got a feedback on this.
Very soon we will release the final Documentation on how to use WooCommerce with DIVI and Toolset.
You will do this:
1. Assign to Products a Content Template.
2. Then, those content templates can be styled with the DIVI Builder.
3. UN-Assign the DIVI builder from your Shop page. This is crucial. The Shop page should never be edited with the DIVI Builder in this case
4. Create a WordPress Archive and in there, add the Loop as used to.
Choose to use a Content Template (Loop Item)
5. Save everything
6. Edit the Loop Item (Content Template of the WordPress Archive) with the Builder.
We will publish the documentation very soon.
Yes. I already made this process. The problem is that there are conflicts between Bootstrap and the CSS of DIVI, so the elements are not styled correctly.
https://toolset.com/forums/topic/bad-appearance-of-the-elements-of-the-products-woocommerce/
OK, great.
I think then we can close this ticket, because the Bootstrap conflict are not a BUG, and handled in the other ticket anyway.
Is everything as for the workflow working fine now, and clear?
Thank you!
Actually, in my humble opinion it is a bug. You should give a solution so that the appearance of the elements is correct.
We use and deliver a native Bootstrap framework - which needs custom CSS adjustments if a Theme (like DIVI) overwrites these rules with Custom CSS of the theme and re-uses the classes that are also used by Bootstrap.
Unfortunately there is no easy way to solve this for all cases.
In some, you will need some adjustments.
But I am sure in the other Ticket Nigel will be able to help you better - but generally, certain adjustments can simply not be avoided.
In my opinion you should not be based by default on bootstrap.
Toolset Layouts could be based on bootstrap, but each theme compatible with Toolset should have its own CSS system, that is, if you use DIVI you should use the CSS of DIVI for CRED, grids layouts, etc, and if any CSS is not included in DIVI should you implement it for that matter. This would avoid 100% of the problems. The same could be done for Elementor, .....
It would be a little more work on your part, but a great solution for the users of Toolset.
It would mean to create hundreds or thousands of such add ons.
Right now maybe only few Themes are officially integrated, but if we start to modify our (Bootstrap) CSS to play in with the custom styles of certain themes, we will never get to a proper result
Instead the correct result is to make it possible to be used as wide as possible.
This is done.
And, provide support and help and suggestions and eventually even DOC's on certain very heavyweight themes like the DIVI theme so we can then share those ideas and solutions with you in the forums.
I cannot help you here in this thread with this.
I will now mark this as resolved, as the initial issue is resolved.
Please do not hesitate to ask us any details in new threads!
