Compatibility issue between Brizy and LiteSpeed Cache – JavaScript 404 errors

Infofuturo García García

• November 03, 2026 07:55

Hello Brizy Support Team,

We have identified a compatibility issue between Brizy (including Brizy Pro) and LiteSpeed Cache that causes 404 errors when loading certain JavaScript files.

Problem Description

When JavaScript minification is enabled in LiteSpeed Cache, Brizy's main scripts (preview.min.js and preview.pro.min.js) are processed and stored in /wp-content/litespeed/js/.

However, Brizy attempts to load additional JavaScript files (chunks) using the location of the main script as a reference. As a result, these files are requested from the LiteSpeed directory, where they do not exist, causing 404 errors.

Examples:

• /wp-content/litespeed/js/preview.pro.434.021069a0.js

• /wp-content/litespeed/js/preview.584.5696f96a.js

The original files are correctly located within the Brizy and Brizy Pro plugin directories.

Tests Performed

We have updated Brizy to the latest version released yesterday, November 2, 2026, but the issue still persists.

We have also reviewed the changelog for this update and found no mention of any fixes related to LiteSpeed Cache compatibility.

As a temporary workaround, we have excluded the following directories from JavaScript minification:

• brizy/public/editor-build

• brizy-pro/public/editor-build

After purging the cache, all scripts load correctly and the 404 errors disappear.

Questions for the Brizy Team

1. Are you already aware of this compatibility issue with LiteSpeed Cache?

2. Are there any plans to fix how Brizy resolves JavaScript chunk paths when the main scripts are minified or relocated?

3. Do you recommend keeping these exclusions as a permanent workaround, or is there an alternative configuration?

4. Is a fix planned for an upcoming Brizy or Brizy Pro update?

We believe this issue should be addressed so that Brizy can work properly with LiteSpeed Cache's JavaScript optimization features without requiring exclusions.

Thank you in advance for your assistance.

Best regards.

0

• 

  KC George

  • November 03, 2026 13:56

  Hello there,

  In the past, we've encountered similar 404 errors involving LiteSpeed Cache plugin files, and deactivating and then reactivating the LiteSpeed Cache plugin helped resolve the issue. Could you please try this workaround and let us know whether it resolves the problem in your case?

  If this turns out to be a compatibility issue that can be consistently reproduced across different WordPress environments, we'd certainly be open to investigating and addressing it. Once we receive your findings, we'll attempt to reproduce the issue in our testing environment. If we can reproduce it, we'll work with our development team to improve compatibility.

  We appreciate your help in investigating this. Your findings will help us determine the next steps and ensure we address the issue appropriately.

  0

Please sign in to leave a comment.