Note: This option is available in the Pro version 220.127.116.11.
By default, Asset CleanUp Lite/Pro does not trigger when Divi’s builder is used, more precisely when the following query string is in use: et_fb=1. For instance, you might have an “About Us” page and it’s built using Divi. The page builder can be accessed in the front-end via /about-us/?et_fb=1&PageSpeed=off. While you use the builder, no Asset CleanUp optimization rule takes place including unloading CSS/JS as well as minifying and combining it. The reason behind it is to make sure that the editor will load perfectly fine and none of its assets that are built especially for the visual builder are altered in any way.
Asset CleanUp can be used to prevent specific plugins that are proven to be slow in loading and irrelevant to load on the page builder, in order to make the editor load faster (e.g. the whole editor could initialize in 2 seconds, rather than in 10 which would add up to the waiting time if it’s often used). This is recommended to be used only when the editor is really slow in loading and by those who really know what they are doing.
The following constant needs to be added to wp-config.php (note that it should be added BEFORE the line where “wp-settings.php” is required):
define('WPACU_LOAD_ON_DIVI_BUILDER_EDIT', true); /** Sets up WordPress vars and included files. */ require_once(ABSPATH . 'wp-settings.php');
The moment this constant is set to true, some of Asset CleanUp’s rules will take effect on the builder which are the rules from “Plugins Manager” and the unload rules set within the CSS & JS manager for the targeted page, in our example /about-us/. In order to make sure the right RegEx rules are set in “Plugins Manager” if you want to unload entire plugins on the editor’s page, you have to make sure to include et_fb=1 in the RegEx. For instance, to match the URI /about-us/?et_fb=1&PageSpeed=off the following RegEx could be used: #/about-us/\?et_fb=1# (see the print screen below).
REMEMBER: You can also just use #\?et_fb=1# to match any page (not only “About Us”) that is having the Divi builder in use. It should work well in most situations.