Rogier Lankhorst

Hi @mplanet5,

Can you list the following information?

– WordPress version
– PHP version
– List of plugins
– Theme
– Is there any customization in the code?
– Do you also have the issue with debugging disabled? I see a lot of errors on your site, that might break things as well.

@mplanet5 if you go to tools / site health / information, you have a button “copy site info to clipboard”. Can you paste that info here?

Do you mean it also doesn’t work with Litespeed cache?

As far as I know nothing has changed in Burst that could impact the way it works with caching plugins.

If you add ‘burst-statistics’, that should do the trick I think!

If you can’t update to WordPress 6.6 yet for some reason, I have here a new version with a fix to ensure WordPress 6.5.5 will also work.

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

To install:

– deactivate your current Burst plugin.
– Download the zip from the above link by clicking the green button
– Upload and activate through Plugins – add new, upload.

This fix will be included in the next update as well.

@ag86nl14 I noticed you’re not on the latest WordPress version, so I tried with your version, and discovered that there is a compatibility issue with the older version of WordPress.

As a quickfix, you can update to the latest version of WordPress. In the meantime, I’ll investigate what is causing the incompatiblity, and see if I can resolve that.

@nickdgreen is it possible to exclude the burst-statistics paths from WP Meteor? That should resolve the issue then.

@nickdgreen I’m sorry, but that’s not possible, it’s not allowed to share credentials in any way through this forum, otherwise I’m in big trouble with the mods, even failing to say this can get me banned ??

But I think we can get a long way through the forums!

I think the problem is a combination of caching and settings.

The first step is to ensure that your caching plugin is not causing the issue. So please deactivate it first.

An important thing I just noticed when running some tests, is that the blocked scripts in Complianz are cached for 30 minutes. So after making any changes (to statistics consent for example), you’ll need to either wait 30 minutes, or add ?cmplz_nocache to your URL when you visit the site, to clear the cache.

If I do this in my test environment, and set ‘ask consent for statistics’ to ‘no’, then I immediately see the visits in the statistics dashboard again.

If the issue is with your caching plugin, please exclude it from any optimizations/concatenations.

@nickdgreen thanks for your detailed input, I’ll test with those settings to see what the problem is.

@ag86nl14 Please let me know what WordPress version you are using, and if you also have the issue with all plugins deactivated.

@soundergy In your case, this is related to the settings in Complianz. If you have selected “ask consent for statistics”, burst will be blocked until the user has given consent.

@shayshay18 Also: Are you on the latest WordPress version? And do you also have this issue with all other plugins deactivated?

What WordPress version are you using? And do also have this error with all other plugins deactivated?

@shayshay18 can you try to install the wp debugging plugin, then visit the Burst dashboard, then check if you see any Burst related PHP errors in the debug log?

Additionally, can you check what errors you seen in the browser console? right click on screen, the “inspect element”, console.

@roccoh do you maybe have the Gutenberg plugin installed?