lugofu

Hello @cteduard,

Thank you for your reply. After a few more tries, I don’t think the problem is with the theme configuration or the site itself: in fact, it recurs on all the sites I’ve created with the Blocksy theme from the moment I try to open the “Customize” page on Chrome from my PC.

The “Customize” page opens fine on other browsers and… on Chrome too when I use it on my Mac.
I tried on another PC with Chrome as well, and again the problem occurs.

My hypothesis is that there was a problem with a recent update of Chrome for Windows. I uninstalled the browser completely on PC, rebooted and tried again. I’ve opened the “Customize” page a dozen times and it’s displayed correctly! I’ll see in the next few days and with other sites if the problem reappears or not, but for now it seems solved!

I’ll come back to you if I’ve made a mistake in my hypothesis and if the problem reappears.

Many thanks again for your help and availability.

Best regards

Hello,

Thanks for your feedback. I recorded a short video this morning to show you what the problem looks like.

I’ve tried to open the page with another browser than Chrome (Mozilla Firefox): the loading time is quite long, but the ‘Customise’ page eventually appears.

To see if the problem is with Chrome, I’ve tried to open the ‘Customise’ page of another of my sites that has Blocksy installed (and for which I’ve had no problem opening the page until now) using this browser: now the same problem appears, which leads me to believe that there may be a problem with Chrome since the latest theme updates.

What do you think?

Thanks in advance for your help,

Kind regards

Hello @rogierlankhorst,

Thank you for your help. I followed the instructions you gave. When I install the zip folder, two things happen:

• the plugin dashboard is accessible again;
• there are no errors in the console but a message :

JQMIGRATE: Migrate is installed, version 3.4.1

styled-components: it looks like an unknown prop “right” is being sent through to the DOM, which will likely trigger a React console error. If you would like automatic filtering of unknown props, you can opt-into that behavior via <StyleSheetManager shouldForwardProp={...}> (connect an API like @emotion/is-prop-valid) or consider using transient props ($ prefix for automatic filtering.)

When I put back the ‘normal’ version of the plugin, the problem reappears, with the following errors:

JQMIGRATE: Migrate is installed, version 3.4.1
416.755d05bc797565475998.js:1 Uncaught TypeError: Cannot create property 'webpackChunkburst_statistics' on string ''
    at 416.755d05bc797565475998.js:1:48
index.e4565fa59245cc2eb245.js?ver=e4565fa59245cc2eb245:1 Uncaught (in promise) ChunkLoadError: Loading chunk 416 failed.
(missing: https://chanvredc.com/wp-content/plugins/burst-statistics/settings/build/416.755d05bc797565475998.js)
    at o.f.j (index.e4565fa59245cc2eb245.js?ver=e4565fa59245cc2eb245:1:53758)
    at index.e4565fa59245cc2eb245.js?ver=e4565fa59245cc2eb245:1:51609
    at Array.reduce (<anonymous>)
    at o.e (index.e4565fa59245cc2eb245.js?ver=e4565fa59245cc2eb245:1:51574)
    at index.e4565fa59245cc2eb245.js?ver=e4565fa59245cc2eb245:1:57160
    at Ur (react-dom.min.js?ver=18.2.0:10:73411)
    at El (react-dom.min.js?ver=18.2.0:10:93232)
    at react-dom.min.js?ver=18.2.0:10:91974
    at xl (react-dom.min.js?ver=18.2.0:10:92039)
    at fl (react-dom.min.js?ver=18.2.0:10:85808)
679.47b1cf43b261994c8e9d.js:1 Uncaught TypeError: Cannot create property 'webpackChunkburst_statistics' on string ''
    at 679.47b1cf43b261994c8e9d.js:1:48

To answer the question you asked (the difference between sites on which Burst works perfectly and sites on which it doesn’t), here are the observations I can give you from my side:

• Difference in host: the site with the bug is hosted by Infomaniak, all my other sites are hosted by oswitch.
• E-commerce site: the site in question works with Woocommerce, which is not the case for the others.

I don’t know if this information makes things clearer for you.

Thank you very much for your feedback.

Have a nice day!

Hi Amir,

Thank you so much for your quick reply!

I had already tried deleting/changing/activating/deactivating the cache plugin + clearing my browser cache, but without success.

I think the problem was actually due to a bug that occurred during the migration of the site; having exhausted all my options for resolving it, I restored the previous version of the site (fortunately, I only lost a few hours of work because my last backup was very recent, and more importantly… the problem was solved!) I was then able to migrate the site, and this time the plugin seems to be working perfectly well.

Anyway, thanks again for your help !

Best regards,

Lucile