CWP Pro 1.3/1.4 – Missing jquery.sparkline.js breaks PHP, ModSecurity and dashboard functions

Hello,

I am experiencing a CWP admin interface issue on multiple servers, and I would like to know whether anyone has already found a fix or workaround.

The problem occurs both:

• on a fresh CWP installation; and

• after upgrading working CWP 0.9.x installations to CWP Pro 1.2, 1.3 or 1.4.

The affected systems run AlmaLinux 9.x latest

Several essential CWP functions no longer complete their AJAX operations. For example:

• PHP installation;

• DNF update;

• ModSecurity installation;

• some dashboard and main-page lists.

The loading icon keeps spinning, while the browser console reports the following errors:

GET https://hostname:2031/<CWP_ADMIN_SECURE_PATH>/admin/design/charts/sparklines/jquery.sparkline.js
net::ERR_ABORTED 404 (Not Found)

blank.js:13 Uncaught TypeError: $(...).sparkline is not a function
    at blank.js:13:13

Another error is also displayed on some affected pages:

Uncaught TypeError: Cannot read properties of undefined (reading 'ext')

The first error appears to be the primary problem: CWP’s own admin interface requests:

/admin/design/charts/sparklines/jquery.sparkline.js

but the file is not available at that location. Consequently, the sparkline() function is undefined, and CWP’s blank.js fails.

CWP support has already corrected part of the underlying installation problem, but these frontend errors remain and prevent several admin functions from working properly.

I have also noticed that CWP’s directories contain a node_modules directory. This raises another possibility: perhaps the affected CWP release requires an internal frontend asset build or deployment step that was not executed, failed silently, or was omitted from the installation/update process.

There may be a CWP-specific build command, deployment script or package-maintenance command responsible for copying the JavaScript dependencies into the public admin asset directory.

Has anyone encountered and resolved this in CWP Pro 1.3 or 1.4?

In particular, I would appreciate information about:

1. Where jquery.sparkline.js is supposed to be installed in the current CWP version.

2. Whether the CWP packages or node_modules contain the file under another path.

3. Whether there is an official CWP asset build, deployment or repair command that restores the missing frontend files.

4. Whether the installer or updater normally runs an npm, Webpack, Gulp, Vite or other asset-processing step.

5. Whether a package reinstall can safely restore the missing assets.

6. Whether copying or symlinking the file from its actual location is a safe temporary workaround.

7. Whether additional JavaScript dependencies are missing, which might explain the reading 'ext' error.

If someone has a working CWP Pro 1.4 installation, it would also be helpful to compare:

• the relevant package.json scripts;

• the location of jquery.sparkline.js;

• the contents and permissions of the public sparklines asset directory;

• any CWP installer or updater logs related to frontend asset deployment.

The relevant public directory may be similar to:

/usr/local/cwpsrv/htdocs/resources/admin/design/charts/sparklines/

or another corresponding directory used by the current release.

For safety, I do not want to run npm install, npm update or an unknown build command inside CWP’s production directories without first identifying the official CWP procedure. Such a command could change dependency versions or overwrite vendor-managed assets.

Any confirmed workaround, official command, package name, file location or diagnostic result would be very useful. I can also forward the technical findings to @Sandeep B. . at CWP support to assist with the permanent correction.

Thank you.