[Resolved] Possible conflict with Divi Builder

[Author]

Posts

[davidL-7]

Hi, we're using the Divi theme (Divi 3.16.1) and having an issue with the Divi Builder Timing out when trying to edit a post. I researched the issue and applied all of the suggestions I could find, to include upgrading to PHP 7.2, increasing memory to WordPress, etc. I went through the plugin conflict check and was able to make the issue go away when I turned off the Toolset Views plugin (v2.6.4.2).

I've included the debug information. It's worth noting that on our last Toolset Views update we did have to do a manual install (downloaded the latest version, upzipped it and FTP'd the files into the /plugins directory).

We also have a staging copy of the site that demonstrates the same issue and can provide admin access to that if needed.

Thanks in advance for any insight you can provide!

[Nigel]

Hi David

If the Divi page isn't loading completely I would expect to see an error or warning in the logs which points to why.

Could you check your PHP logs?

If you haven't already, turn on the debug log by editing your wp-config.php file and change the line with WP_DEBUG like so:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

That will create a file debug.log in your /wp-content/ directory which you can examine in any text editor. Try visiting the same page which fails to load and then inspect the log. If you don't find the debug.log file it means it didn't generate any warnings or errors.

Let me know what you find so I can see how to proceed.

[davidL-7]

Thanks Nigel! I followed your directions, generated the debug.log and noted a series of errors indicating missing files in the View plugin. So evidently when I did the manual install, all of the files didn't make it up (some glitch in the FTP process I suppose). I reinstalled Views manually and the issue was resolved.

Thanks again for the tip!

On a related note, we use Toolset plugins on almost all the WordPress sites we develop. We love Toolset, but we often encounter issues when running plugin updates. I think it's just the sheer number of files involved, increasing the likelihood of some kind of interruption. I'm wondering if it would be possible for updates to have a "patch" version, where you're only updating the files that have changed, not the entire plugin? Just a thought. Thanks again!

[Nigel]

Hi David

We do get quite a few reports where clients have issues updating plugins. Sometimes it's on us—we release an installer update with a bug—other times it is less obvious and may be server dependent etc.

I don't anticipate us switching to an incremental patch system for updates. If we have problems now, I imagine the potential for issues where patches may or may not have been successfully applied or interrupted while partially applied would open up even more possible points of failure (let's all just move to Git).

But it is something we are concerned about, and internally our installer team have been working on adding a raft of debug info that should make it easier when problems arise to diagnose what the underlying issue actually is. That should be rolled out with plugin updates before too long.