Skip Navigation

[Resolved] Divi-Page-Builder not loading with active Content Template for Posts

This support ticket is created 3 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.

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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 12 replies, has 2 voices.

Last updated by Luo Yang 3 years, 2 months ago.

Assisted by: Luo Yang.

Author
Posts
#2133413
2021-08-04_10-22.png
2021-08-04_10-23.png

I am trying to:
Edit a Post with Divi-Pagebuilder.

Link to a page where the issue can be seen:
haitiangermany.com

I expected to see:
The post opening in the Divi Builder.

Instead, I got:
Clicking the edit-link of a post with content template results in an 302 response and gets redirected to the standard-post-link.
Console error "ET_Builder is not defined"

When the Content Template for Posts is editing posts works flawlessly.

I've already contacted Divi support and this problem is not known.

#2134381

Hello,

I have searched the keywords "ET_Builder is not defined" in our forum and our to-do list, I don't find any result.

So it is not a known issue, how do you setup the edit-link of a post? did you get any feedback from "Divi Builder"?
Are you going to edit the post in WordPress admin side?
If it is, you can try the shortcode: [wpv-post-edit-link], see our document:
https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-post-edit-link

#2134487
2021-08-05_10-05.png

Divi seems to use a GET-parameter to load up the Visual Builder (like most Page Builders do, I think) when editing a post.

When Toolset's content templates are activated for posts this link (e.g. /this-is-a-post-name/?diviparam) gets redirected (per HTTP 302) to the post-url itself (e. g. /this-is-a-post-name/)

This seems like a server- oder permalink-configuration problem at first.
However, this problem does not occur when the content template for posts are disabled.

Which leads me to the conclusion that the problem may lie within Toolset.

Does Toolset affect the redirects , URL-rewrites or HTTP-headers in any way?

#2134559

No, Toolset plugins won't affect the redirects, and your screenshot shows you are in frontend.

You can try these:
1) Deactivate all Toolset plugins, check if the problem still persists
2) If the problem is fixed, then it might be a compatibility issue, you can provide a copy of your website, also point out the problem page URL, provide detail steps to reproduce the same problem, I need to test and debug the problem in my localhost:
https://toolset.com/faq/provide-supporters-copy-site/

#2137363

Thanks for the details, I can download those files, please point out the problem page/post URLs, where I can see the problem you mentioned above: Console error "ET_Builder is not defined"

thanks

#2143531
2021-08-16_09-46.png
2021-08-16_09-42.png

Dear Luo,

the problem occurs when editing any post created with Divi Builder in this installation.

Clicking the edit-link should load the Divi-Inline-Builder, but the editor keeps on loading and the above mentioned error message shows up in the console - as mentioned above, this does not occur when Toolset is disabled (the error also disappeares when only disabling the Toolset Template for Posts)

Also see attached screenshots.

#2143637
divi2.JPG

I have tried the duplicator package in my localhost, it works fine, see my screenshot divi2.JPG

So there should be other server issue in your website, please try to get the PHP debug logs from your website:
https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/#php-debugging
section "PHP Debugging"

#2143647

And it might be a browser problem, please clear your browser cache or try with another browser and test again

#2143687

Dear Luo,

I think Toolset is not activated in your local installation above. (no Toolset-entry in menu in your screenshot)

I also intalled from this archive locally and CAN replicate this problem, but needed to activate Toolset-Plugins before.

#2143757

We now also have further informations regarding this problem -
we can narrow this down to the following versions of toolset:

Toolset Blocks starting with v1.5.2 (1.5.1 last working version)
Toolset Forms starting with v2.6.9 (2.6.8 last working version)
Toolset Types starting with v3.4.11 (3.4.10 last working version)

As mentioned, and maybe useful for further debugging / forwarding this to your development-team -
we think this bug relates somehow to the way wordpress or toolset handles redirects:

wp_safe_redirect
do_action('template_redirect')

As temporary solution we downgraded all our production-sites to the above mentioned versions of toolset.

Let me know if we can be of any further help!

#2144373

Thanks for the details, I can see the same problem in my localhost with your duplicator package, and I have escalated this issue, will update here if there is anything news.

Currently, if you are using the latest version of Toolset Blocks plugin + Divi theme, you can try this:
ashboard-> Divi-> Theme Options-> Builder-> Advanced, disable option “Enable The Latest Divi Builder Experience”, and test again.

#2232307

Are there any news on this topic?

#2232817

Hello,

We have created a erratum for it:
https://toolset.com/errata/js-errors-editing-posts-with-divi-divi-builder-fails-to-load-for-posts-using-a-toolset-template/

See the workaround:

Being unable to edit posts with Divi if a Toolset Content Template is assigned to the post falls foul of the advice not to mix Divi and Toolset, and even if it is something that used to work, we have other priorities and there are currently no resources assigned to work on this issue.

The only workaround for the time being would be to either temporarily disable Toolset Blocks while editing such posts, or to remove the Content Template assignment while editing the post, and re-assign the template once editing is complete.