Blocksy Theme Conflict

  • Martin

    (@rockso)


    3 days, 4 hours ago

    Hi,

    i have been testing this plugin with the Blocksy Theme + Woo. When wp ghost Lite mode is activated, the add to cart quantity buttons (+ & -) do not work. This is site wide, so on the product page, the product archive, the popout cart, classic basket and classic cart.

    This is the error returned in the browser console:

    main.js?rnd=1:6 Uncaught (in promise) ChunkLoadError: Loading chunk 902 failed.
    (missing: https://MY TEST SITE/core/views/a8532ddfd5/static/bundle/902.882326f54bd66fcdce7b.js)
    at Object.j (main.js?rnd=1:6:4198)
    at main.js?rnd=1:6:1971
    at Array.reduce ()
    at o.e (main.js?rnd=1:6:1937)
    at load (100.957a1d57641c41d5237c.js:1:1667)
    at n.6555.s.length.d.length.d.forEach.e.id.s.map.t.hasLazyLoadClickListener.t.addEventListener.e.once.once (main.js?rnd=1:1:3259)

    The toggle that causes this is
    WP Admin>WP Ghost>Change Paths>Theme Security> Hide Theme Names

    I have tested other dir, theme, plugin masking mods and they do not cause this issue, so I don’t know why WP Ghost is causing this.

    Cheers,

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Peter

    (@petersquirrly)

    3 days, 3 hours ago

    👋Hi Martin,

    Happy to help with this.

    You isolated it to Hide Theme Names, with every other masking toggle clean. That tells me something specific: Blocksy’s numbered chunk files (like 902…js) aren’t part of the enqueued scripts WP Ghost rewrites in the page source. They get requested at runtime from a path baked into Blocksy’s own compiled main.js. Rename the theme directory, and that runtime request can point somewhere WP Ghost isn’t serving from. That’s your ChunkLoadError.

    We shipped a Blocksy fix in version 8.3.07 (16 March 2026). Current version is 9.0.03. If you’re on anything older, update first, clear all caches (WordPress, CDN, browser), and retest with Hide Theme Names back on.

    Until then, keep Theme Security on for everything except Hide Theme Names (custom themes path, hidden inactive themes, renamed style.css). Only the active theme’s own name stays visible to class-level scans, nothing else changes.

    Thread Starter Martin

    (@rockso)

    2 days, 8 hours ago

    Hi, thanks for getting back to me. I’m using Blocksy 2.1.56.
    Is this + & – problem due to the specific mechanics of you plugin?

    I did originally create my own mask via functions.php & .htaccess which worked to front-end remove the theme name etc. But it was a bit of PITA to maintain.

    Then I came across WP Hide & Security Enhancer, which can rename the theme and cause no conflicts with the + & – buttons. But it lack the features your’s has to mask other dirs not detected (e.g: url masking for /wp-content/uploads/blocksy/css/… and CSS id masking id=’blocksy-ext-woocommerce-extra-styles-css)

    I don’t wanna be running tow plugins side by side (though i have tested and they can work together).





    Plugin Support Peter

    (@petersquirrly)

    2 days, 7 hours ago

    You can keep WP Ghost handling everything (uploads masking, CSS ID masking, etc.) except Change Themes Path / Hide Theme Names, turn that one off. In WP Hide, enable only its theme masking, leave its other path options off. No double rewriting, buttons stay working, you keep every feature.

    On the “why” question, yes it’s our side. WP Hide handles nested runtime asset requests differently than our rewrite engine does.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Tags