The dashboard Burst does not charge

@lugofu can you try clearing your browser cache? I just double checked the current live plugin, it loads fine on my test environment. The fact that it works when trouble shooting is enabled suggests that the browser has old code in the cache.

You can also try loading in a different browser, to ensure that there is no cache.

Hello @rogier Lankhorst,

Thank you for your prompt reply. I should have mentioned this in my first post, but we had already tried unsuccessfully to display the Burst dashboard using different browsers and devices. And if I look at my other sites from the same browser, the Burst dashboard is displayed as usual. Only one site seems to be affected, which suggests that this is where the problem lies. I’ve also tried uninstalling and reinstalling the plugin, but the problem persists.

Do you have any other ideas for solving this problem?

Thank you very much for your help.

@lugofu sometimes the hosting has a very persistent caching. If that is the case, there probably is a function on the hosting environment where you can clear the server cache.

Do you have more console errors apart from the chunk load error?

I am experiencing the same issue, the dashboard isn’t loading. I cleared the website cache, as well as the browser cache, nothing helps. This issue came up with the latest update. This is what I get while inspecting in the console:

416.755d05bc797565475998.js:1 Uncaught TypeError: Cannot create property 'webpackChunkburst_statistics' on string ''
    at 416.755d05bc797565475998.js:1:48
679.47b1cf43b261994c8e9d.js:1 Uncaught TypeError: Cannot create property 'webpackChunkburst_statistics' on string ''
    at 679.47b1cf43b261994c8e9d.js:1:48
index.e4565fa59245cc2eb245.js?ver=e4565fa59245cc2eb245:1 Uncaught (in promise) ChunkLoadError: Loading chunk 416 failed.
(missing: https://ssnm.org.mk/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)

I also have this same problem but only on one of the 13 sites that I manage. Bizzare!

As this issue does not seem to occur consistently, and we can’t reproduce it, I hope I can get your help in finding the cause. I have created a branche on GitHub in development mode, which should make resulting errors more transparent.

If you can do the following:

– deactivate and delete the current plugin (choose to keep the data of course!)
– Go to https://github.com/Burst-Statistics/burst/tree/debug-build
– Click on the green button ‘code’, and choose ‘download zip’
– in WordPress, go to plugins, add new, upload. Upload the new zip file and activate
– Now go to the settings page. Right click on the screen, “inspect element”, “console”.
– In the console, copy the errors you see there.

Please post those errors here. I hope to be able to find the cause this way!

@manhire is there something on the website where it doesn’t load that distinguishes it from the other sites? Like: language, plugins, security setup etc?

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!

Thanks for your input. Because it works in dev mode, which is essentially the same code, I think it’s worth a try with completely re-generated code. I have created a branch here:

https://github.com/burst-Statistics/burst

Installation is the same as with the previous branch.

Let me know if that resolves the issue!

Hello @rogierlankhorst,

Thank you very much for your help: I’ve just installed the compressed folder downloaded from GitHub, and it seems to solve the problem! The dashboard is back to normal.

Once again, many thanks for your professionalism and responsiveness.

Have a nice day!

@lugofu great! Thanks for confirming. @manhire @apollosk we will release an update early next week which should resolve the issue for anyone else that has this issue.