I read that thread and will query with Mercedes who, and why, gave her this information.
We integrate the DIVI theme.
None of any other Themes of that house is integrated.
This does not mean it doesn't work, but as we see, it (the theme) customizes things that it should not, seen from the compatibility point of view.
Well.
I made some more tests, and have a question:
1. Do you even plan to use Layouts?
Because if so, you will re-create the templates anyway and will integrate the Theme as above elaborated.
Then the issue would be solved.
2. The Theme you use cusomtises practically all elements also used by Bootstrap.
There is no way for us to consider that.
You can either load our Scripts or the Theme's.
Beda,
With EXTRA or DIVI it is very easy to create a website.
My idea was to use Toolset only for pages or sections that required special behavior that I could not do with EXTRA / DIVI. In the video of your article (https://toolset.com/2017/06/divi-integration-with-toolset-the-first-update-is-out/) shows how to make pages integrated with DIVI, or integrate 'Fields and Views, CRED Forms and Access' using the DIVI text module.
This is what I need to use in my WEB.
I can not now recreate all the pages on the web with Toolset, this would be an immense work and would not make any sense, since DIVI / EXTRA allows to do things much more easily and visually than Toolset. The logical thing is to use Toolset only for certain special things.
What I do not understand is why you did not have problems with the DIVI theme, and now you have so many problems with the EXTRA theme.
Both, DIVI and EXTRA, are the themes most used by users of Elegant Themes, all others are outdated.
Also, I'm seeing on the internet that you have many more problems with other themes, for example, AVADA. Perhaps the technology you have chosen for integration with other themes is not the most appropriate, it is logical that Toolset use the CSS of each integrated theme for rendering, not force to Bootstrap.
Best regards,
Francisco R.
In this case, you should deactivate Layouts and select "This site is not using Bootstrap CSS".
This will work just fine.
What you will not be able to use is Bootstrap Styles and rules, you will need to add responsive HTML on your own, to as example Views Loop Outputs.
It is not logical to not force Bootstrap.
Layouts needs it. Views Loop (specific features) need it.
If you load Bootstrap, but another tool is hijacking those classes and adding it's own, without renaming them, it is not a problem of Bootstrap but of that framework that accidentally uses the same class names.
It would be very easy for the Theme authors to just add a class name and address only that class name with his/her CSS.
This will also avoid future conflicts where users might want to use Bootstrap in that Theme.
As I have seen in your video of the integration with DIVI, I can use Layouts and DIVI perfectly, I also need to do this with EXTRA in my web. I do not want to disable Layouts. If the team of Elegant Themes does not give me a solution to this problem I will have to ask for the refund of Toolset.
The problem is the time you made me lose by telling me that Toolset was compatible with EXTRA. 🙁
You can use Layouts and DIVI because we provide an integration.
There is no way to use Bootstrap on the EXTRA theme.
No way. Not even with Custom HTML.
This Theme overrides Bootstrap Classes and it can only be avoided by either fixing the Theme or adding lots of Custom CSS.
I apologise that you have been told this will work smoothly, and I will report that, as it is simply not true and you should have been informed about the potential conflict that can but must not, surge when a theme is used.
You have not been informed properly, I acknowledge that and if you require a refund I will help you to get it, no matter at what time.
It is just justified.
Now, I really would like to make this work for you.
Why don't we start to talk to the folks at the EXTRA theme?
Maybe we can achieve something, no?
Would you agree to that?
Then I would contact them myself.
Yes. I agree.
I have already written a ticket to Elegant Themes support, but have not yet responded.
If you can get in touch with them directly we may have more strength for them to do something.
Thanks Beda.
If you could share the link with the Developer of Elegant here, that would be cool.
I already filed an internal Ticket so to start some contact.
This is the ticket link:
enlace oculto
But they have not answered anything yet. 🙁
It seems private.
Anyway, please keep us updated on it.
Beda,
I have been told the following.
Is this correct?
--------------------------------------------------------------------------------------
Hi Francisco,
In my opinion, it actually is a plugin problem because the .container class is used in a lot of themes, the plugin should simply add a prefix for their containers so it doesn't change this on the theme. They could have used .toolset-container or something similar.
Go to Extra > Theme Options > Custom CSS and add the following:
.container {
width: 90% !important;
max-width: 1280px !important;
}
This should overwrite the plugin's CSS, let me know.
Thank you,
Vlad Patrascu
--------------------------------------------------------------------------------------
Beda,
I have tried this code and it does not work.
I told Vlad you wanted to talk to him directly.
With a little CSS Vlad has solved many problems.
.container {
width: 90% !important;
max-width: 1280px !important;
}
.container::before, .container::after {
content: none !important;
}
However, there are still some problems. Vlad is looking at these problems.
I have also noticed now that when I am in the WPML 'translation editor' of a post or page, and I click on the 'Save and close' button, although it has very few elements, the page or post is very delayed in saving and closing the translation editor. Now this is independent of whether or not I have the Toolset plugins active.
I have also noted that the description is not displayed now on WooCommerce products. I have tried to correct it with 'WooCommerce Views', but I have not been able to. How can I do to see the description again as it looked when Toolset was not installed?
Look at the screenshots.
Thanks.
Best regards,
Francisco R.
Beda,
In addition to the problems I mentioned in the previous message.
There is another issue related to Toolset and the web store page.
On the store page, when Toolset is active, the language change (WPML) menu option disappears. If I turn off the Toolset plugins it shows again.
Look at the screenshots.
Thanks for your help.
Best regards,
Francisco R.
Hi,
Vlad has made some suggestions in a message that I put next:
------------------- Vlad Message -------------------------------
There might be other problems that are yet to be discovered. WP Toolset should definitely use a prefix for common classes like .container, .row, .nav or a namespace for all of them.
This is what I propose.
1- Use a namespace like .wp-toolset for all Bootstrap classes.
2- Have a wrapper container for the toolset content which will use the .wp-toolset class.
This is how it would work.
<div class="wp-toolset">
<div class="container">Content</div>
<div class="nav">Content</div>
</div>
.wp-toolset .container { /* code */ }
.wp-toolset .nav { /* code */ }
This way, the CSS will only apply to elements within the .wp-toolset container and any code outside that will not be affected.
Thank you,
Vlad Patrascu
------------- End Vlad Message -------------------------------------
Please tell me something about the problem and how you will solve it so that I can make a decision.
Thanks.
Best regards,
Francisco R.
