Solid Security Pro JavaScript Error on WordPress 7.0 Multisite

Hi @ricdoe2026,

Thanks for the detailed report, the full stack trace makes this much easier to reason about.

That error is coming from the React app that powers the Security settings screen. CORE_STORE_NAME is the plugin’s internal data store, and the message “Cannot read properties of undefined (reading ‘CORE_STORE_NAME’)” means the settings page tried to read from that store before the JavaScript bundle that registers it had finished loading. In other words, one of the settings page script files did not fully load or register, so by the time the page asked for the store it was undefined. The settings UI is split into several script chunks that all have to load together, and if one of them is missing or served in a broken/stale state, you get exactly this symptom while the front end of the site stays perfectly fine.

WordPress 7.0 only released a couple of weeks ago, so it is the newest core, and these admin React bundles are sensitive to how their JavaScript is delivered. The good news is the most common causes of this are on the delivery side and are quick to rule out. In rough order of likelihood:

1. Stale cached JavaScript from before the 7.0 upgrade. After a major core update, the browser and any caching layer can keep serving the old admin scripts, which no longer line up with the new ones. Please do a hard reload of the settings page (or open it in a private/incognito window), and clear any object cache, page cache, and CDN cache. On Multisite, clear these network-wide, not just for one subsite.
2. JavaScript optimization. Any performance or caching plugin (or a host-level asset optimization feature) that minifies, combines, or defers JavaScript can corrupt this kind of split admin bundle and produce precisely this “reading X of undefined” error. If you have anything like that active, please temporarily exclude wp-admin from JS minify/combine/defer, or turn that optimization off, then reload the settings page. This is the single most likely culprit when caches have already been cleared.
3. Plugin version. The plugin is now Kadence Security Pro (Solid Security Pro was renamed). Please confirm you are on the latest available build, since a major core release like 7.0 is exactly when compatibility updates land.

A few details would help me narrow it down if the above does not clear it:

• Does the error happen network-wide, or only on a specific subsite (and does it occur in the Network Admin as well)?
• Are you running any caching or performance/optimization plugin, or does your host apply asset optimization?
• Does it persist after clearing all caches with JavaScript optimization disabled for wp-admin?

If it still throws after caches are cleared and JS optimization is off, please grab the browser console with the Network tab open and note whether any of the plugin’s settings page .js files return a 404 or fail to load, that will point straight at which chunk is missing.

Kind regards,

Pawel P.

Liquid Web Software Support