Deploying this site I find something strange when listing Pages Post Type in the Admin list.
There is at the bottom an unexpected output:
This is the generated shortcode, based on the settings that you have selected:
You can now copy and paste this shortcode anywhere you want.
What's that? It is not an expected output, I'd suggest investigating what this is by disabling plugins and theme to see where it comes from.
In any case, on the Home Page, I see also PHP errors:
Warning: explode(): Empty delimiter in /duplicator/dp-stgz/plugins/wp-views/vendor/toolset/toolset-common/inc/autoloaded/utils/Attachments.php on line 45
I notice, the wp-content folder is renamed, and there is an error related to Toolset here, it's related to code that gets Images in the database by ID.
On that home page, the builder results NOT ACTIVE.
There is another error on the backend:
Failed to load plugin url: <em><u>lien caché</u></em>
Notice the URL is all messed up?
First we see that the wp-content is renamed to dp-stgz, but then in this last URL, there is a totally missing / slash and instead - is used!
This is not something Toolset can do unless edited manually or the renaming of WP Content Folder was done wrong.
It seems literally to cal twice another URL
Of course, if debug mode is turned off you will never see those issues - but that doesn't mean it will still work as supposed.
When I try to edit a page with the builder on this duplicate, the builder never loads.
So, in this duplicate, I cannot see the issue, as it's somehow broken (that maybe only on the Duplicate or on the live site as well, I am not sure)
I've checked the other testing URl you provided, lien caché, there is however no Divi Edited Homepage there.
Also, the View mentioned is not existing (wp-admin/admin.php?page=views-editor&view_id=17)
I found finally this lien caché, where the issue seems visible.
I see there you insert (with the builder) [wpv-view name="view-allo"], and that View, in turn, has a Content Template for the Loop.
The best solution to not allow Divi or the Builder to add it's classed in the Views loop, in this case, is passing the Content Template like this:
[wpv-post-body view_template="loop-item-in-view-allo" suppress_filters="true"]
See, we add a suppress_filters="true", this means, other software will not be allowed to hook into the content rendered by Toolset, and hence, even if Divi or the builder add DIV's where not required, those won't appear on Toolset Content Templates - since you suppress their filters.
Or, as Minesh elaborated you might not use a Content in the View - which has a similar effect.
The root cause to this however seems not on our end, it's Divi/The builder that adds those DIV's to stuff shown thru the_content filter.
We probably cannot solve this in any other manner than suppressing their filter which is done as above shown.
See also https://toolset.com/forums/topic/whats-up-with-et-boc-and-et_builder_inner_content/, https://toolset.com/forums/topic/question-about-very-strange-wrapping-of-of-views-template-in-divi-3-10-1/#post-952322
I think I am now also able to replicate this locally and can confirm as well the solution for this exceptional case:
1. You need to actually design the SINGLE posts of a type (displayed later in Views) with the Builder
2. Then you need a Content Template rendering the View's loop
3. This then should be inserted in a page using the builder
In this case, the builder applies it's styles to the single posts.
That, even if their post data is called in a View loop, and hence, they add the Div
This is clearly to avoid by suppressing filters as there is nothing in Toolset that could stop that (and you would theoretically be supposed to design the CT's with the builder hence never stumble on this issue)
We added that suppress_fiters exactly for this reason.
Note in the DOC:
If suppress_filters=’true’, all third party (non WordPress) filters hooked into the_content filter will be removed, when retrieving the post body. In certain circumstances, plugins using this filter can add duplicated content to the post body – removing the filters can resolve this problem.
That is exactly the cause here, Divi and the Builder hook in the content, add their default DIV, and this simply whenever Divi or the Builder are used to design those single posts.
Is the issue as well resolved for you if you pass suppress_filters?
