Note: This option is available in the Pro version

By default, Asset CleanUp Lite/Pro does not trigger when Bricks Visual Site Builder is used, more precisely when the following query string is in use: bricks=run. For instance, you might have an “About Us” page and it’s built using the “Bricks Visual Site Builder” theme. The page builder can be accessed in the front-end via /about-us/?bricks=run. 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 that none of its assets that are built especially for the visual builder are altered in any way.

There have been plenty of situations when some of the builder’s files were altered (e.g. minified) that ended up in the page builder not loading due to JavaScript errors (visible in the browser’s console) or it was loading, but some of its functionality didn’t work. Thus, it’s best to leave those assets untouched as any optimization is completely irrelevant (it’s mostly for the guest visitor and for Google PageSpeed Insights that accesses the website as a visitor).

However, some users, especially developers who work on various websites are experiencing a very slow load of Bricks’ builder because there are too many plugins loaded on those WordPress websites, which also have lots of CSS/JS that would even interfere with the JavaScript files from Bricks’ builder.

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, 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 slow in loading and by those who 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):


/** 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 bricks=run in the RegEx. For instance, to match the URI /about-us/?bricks=run the following RegEx could be used: #/about-us/\?bricks=run# (see the print screen below).

REMEMBER: You can also just use #\?bricks=run# to match any page (not only “About Us”) that is having the Bricks Visual Site Builder in use. It should work well in most situations.

If the editor has been working fine before and suddenly it stopped working after you enabled this option (placing that code snippet in wp-config.php), it means some of the unload rules are interfering with the Bricks Visual Site Builder and it’s better to deactivate it (remove the snippet) or if you’re keen to still have the editor load faster, then consult with a developer about it by checking the errors from the browser’s console.

Was this post helpful?