[Resolved] Style conflicts with Bootstrap and 3rd Party Plugins or Themes.

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.

This topic contains 51 replies, has 11 voices, and was last updated by  Beda 2 weeks, 5 days ago. The support staff assigned to this topic is Beda.

Viewing 15 posts - 16 through 30 (of 52 total)

Forum moderator

Supporter languages: English (English ) Spanish (Español ) German (Deutsch )

Supporter Timezone: Europe/Madrid (GMT+02:00)

Replicating and fixing these issues I have a question:

In standard WordPress posts the Content Template defined with Toolset covers the whole page, however, in a new CPT the Content Template defined with Toolset does not cover the whole page.

In my tests, which use:
- DIVI (vanilla settings fresh install)
- Views
- Types
- Bootstrap is loaded by Toolset

I cannot make the fullwidth work.
It does not apply when I set it either for the single post or the content template.
Left and right sidebar work fine.

If I disable Toolset I see that fullwidth means 80% of maximally 1080px, but I cannot make this work with the above steps, the content is always container size no matter if I load or not the bootstrap.

I believe this is a BUG, where the settings are not respected in Content Templates
Can you confirm this as well?


If I have not misunderstood you, my conclusions are the following:
1) A content template for the posts can take the whole width if Bootstrap is not connected. If Bootstrap is connected leaves on both sides (right and left) of the page some small strips. See the screenshots.
hidden link
2) A content template for a new CPT, in my case 'Base de conocimientos', even if it has a configuration similar to the content template of the posts, does not take the entire width of the page regardless of whether Bootstrap is connected or not. This looks like a Toolset Views bug independent of Bootstrap. See the screenshots.
hidden link
Beda, Is this what you asked me?


Forum moderator

Supporter languages: English (English ) Spanish (Español ) German (Deutsch )

Supporter Timezone: Europe/Madrid (GMT+02:00)

I do not see how I could make full width work - as I outlined earlier it does not apply, no matter on what post type.
It always stays container width

It's a missing class in the body class:

I reported this to the Developers.

The margin you saw, are probably the same as elsewhere:
Bootstrap uses paddings of 15 pixel - that is not used by DIVI, so it changes the appearance.
That is also reported.


Do not forget to tell them all the appearance problems of the header.
Thanks for your help Beda.


Beda... check out hidden link ... I bought this plugin, and they were able to figure out the full width thing.


Dear ,

I do not know if this is the place to tell my issue but after installing the toolkit my site is now like garbage and all my efforts are gone. I have to publish my site this week as I promised my fans.
I only purchased this to make a form for adding a product by vendors and now I lost the whole day trying to minuplate with the css file.
I did choose this (This site is not using Bootstrap CSS)
but no lock.
if you can fix my site tomorrow would be great otherwise I have to take my money back and go purchase another one.



can you delete my post because it is now fixed by your support.


Forum moderator

Supporter languages: English (English )

Supporter Timezone: Africa/Cairo (GMT+02:00)


I'm Mohammed, the Toolset support team leader.

I'm posting here just to inform you that Beda is not working these days.I've asked another supporter to handle your request.

Please wait and we will be in touch with you again very soon.



Any advance in these problems?
Please, it would be good to already have a solution for all these problems.
Best regards,
Francisco R.


Nobody says anything? 🙁


Forum moderator

Supporter languages: English (English ) Spanish (Español ) German (Deutsch )

Supporter Timezone: Europe/Madrid (GMT+02:00)

I apologize, as I was on vacation and came back just now.

No, there has been no work so far.
I gathered all issues, showed why they happen and proposed solutions.

I can show you a transcript:


Tests made with DIVI from elegant themes (vanilla) and Toolset Types + Views, having the settings turned to "Toolset should load Bootstrap 3.0".

All tests are chronological from install > Visit HomePage > Visit Posts > Visit Pages > Visit Custom Posts.

1. Link Styles overwritten by Bootstrap (especially in the Menu Items):

.nav > li > a:hover, .nav > li > a:focus  background-color: #eeeeee; 

==> Should be changed in the Theme by adding a custom class to the href elements.

==> Or you need to add custom CSS to re-style the hover text color of DIVI, with an !important .
Not really the best solution.

2. All items added to HTML by DIVI that use the class "container" will be overwritten by the Bootstrap Classes for "container"

==> Should be changed in the Theme by adding a custom class to the containers, not using a vanilla name like "container"

==> This has the effect that if you look at your template with "This site is not using Bootstrap CSS" you will see exactly what DIVI outputs, when you activate "Toolset should load Bootstrap 3.0" things will get margins and paddings added by Bootstrap.

==> The main reason why DIVI should change this and not Toolset or Bootstrap is, they call this "Fullwidth" template.
But they add width: 80%;max-width: 1080px; while they do not pass a padding, which Bootstrap does, hence overwrites it.

3. Divi adds a padding to all "ul" items

padding: 0 0 23px 1em;

which affects for example "wpv-pager-nav-links" since it'll now have a "1em" padding to the left.

4. Select fields are completely overwritten by Bootstrap, through our ".form-control" class.
This should be expected, as we provide a Bootstrap syntax. If you do not want to use that, but theme's, then it can be disabled in the View when inserting the Searches (Legacy code)

We could say the same for pagination elements using bootstrap.

These are the main issues seen, + the ones appearing when you begin to use WooCommerce, but that requires another round of tests.

Then there is a Bug, on Toolset side, where Fullwidth background not applied to Content Templates.
That is reported and has been solved here:

Now, I tried to expedite a decision on these issues, because as you see, they are not solely on Toolset.
They require a careful decision, wether to hack or to not hack, wether to document it or not, etc.

The issue is on the Lead Developer's to do list, and when they reach this task I will get notified with the decisions.

I cannot suggest any thing else but to add Custom CSS to fix the issues, for now.

You may use the feedback form if you wish to enter in contact with the Management about this issue, I can assure that the issue is properly reported and debugged, but I cannot provide you the official decision and fix, as there is none yet.

I apologize the delay, and thank you for understanding.


It has been quite a while since the beginning of all the problems, I hoped that all these problems were already solved.
If the problems are going to be solved in the course of 1 month I could wait, but if the problems are not going to be solved at that time then you should now provide me with a workaround to solve them.

Best regards,
Francisco R.

Beda had created a new ticket for one of the issues reported and you can see it here https://toolset.com/forums/topic/avada-globals-conflicts-with-toolset-bootstrap/

Beda had created a new ticket for one of the issues reported and you can see it here https://toolset.com/forums/topic/total-theme-conflicts-with-toolset/


There is a permissions issue in your support forum. This is showing as one of my tickets but it's not.

Viewing 15 posts - 16 through 30 (of 52 total)