Rogier Lankhorst

Hi @mqukic,

The page statistics in the admin bar gets updated on a daily basis, so it is possible that it lags behind the statistics on the dashboard. If the scheduled processes/cron jobs are running correctly, it will update after a day.

Can you try if it makes a difference when you deactivate WP Optimize, and if so, exclude ‘burst.min.js’ from the optimizations?

Great! We’ll merge this fix in one of the coming updates, please check the changelog before updating!

@apollosk I made another adjustment, can you try again?

Sorry for the slow progress, it’s a bit like debugging blindfolded, as I don’t have the issue locally. Hope this one gives us a bit more insight!
https://github.com/Burst-Statistics/burst/tree/decodeURI-try-catch

@apollosk I’m sorry, I’ve made a stupid typo… Instead of the variable ‘uri’, I put ‘url’ in the log. So the error you see is actually one of my own making.

I’ve fixed this now, can you try again?

This should be fine, no need for a full path.

@apollosk sorry for the late response! I did some digging in the code, and while I can’t reproduce the issue, it’s probably something to do with the language encoding/decoding.

I’ve created a version which does some better error handling, and logs the error if it encounters any:
https://github.com/Burst-Statistics/burst/tree/decodeURI-try-catch

Can you try the following:

– deactivate your current plugin
– download this version as a zip using the green button
– Go to plugins, add new, upload, and upload and install this zip file, and activate it.

Then, try the dashboard again. If you see any errors in the console, please post them here.

@aliahads there is no admin interface: it is just an API, which allows a cookiebanner plugin to store consent in a standardized way, so consent requiring plugin knows if it can store data for a certain category. For this to work, the plugins requiring consent and your cookie banner plugin both need to integrate with this API. In the readme you can find which plugins currently are integrated.

Hi @man10101, CF7 and elementor currently don’t integrate with the WP Consent API. Complianz only states that it has a direct integration with them, not that they integrate with the consent api. Besides that: Complianz has abandoned the CF7 integration, due to continuous breaking changes in the js code, so it only works for a very old version.

As both plugins require consent, ( CF7 because of the reCaptcha integration, Elementor because it tracks statistics and stores preferences, and integrates with services like YouTube and Facebook), an integration from the WP Consent API would be the preferred solution. It would also make them compatible with several other cookie banner plugins.

For example, because the CF7 integration in Complianz is abandoned, it’s not possible to ask consent for the reCaptcha service with the latest CF7 version. And because Elementor has directly integrated YouTube backgrounds in the javascript code, it’s not possible to block these backgrounds out of the box.

If these plugins request the consent status from the WP Consent API, they can conditionally load these services int he most efficient and performant manner.

I would recommend to ask both plugins to integrate with the WP Consent API, which would add them to the list already including WooCommerce and Google Site Kit.

@3cstudio I’ve checked this, it’s not the live visitors section: that path is not /track, but /live-visitors. If I have the dashboard open, I see 2 requests each 5 seconds. This adds up to about 600 requests in 25 minutes. I’ll add a limit to that anyway, but this did not cause your issue.

As the requests did not result in any hits in the dashboard, I suspect it is the endpoint test which was somehow failing.

I can’t reproduce it yet, but what might have happened, is that the “last test time” did not update because the test itself never completed, because of a timeout. So maybe the server became a bit slow for several minutes, which caused the test to start over and over.

For this to happen

– the WordPress heartbeat probably triggered the server every x seconds.
– The test response needs to time out on the server for some reason.
– Then the last test time may not be updated, causing the test to start again when wordpress heartbeat triggers again.

I have moved the saving of the last test time to before the test, to prevent this from happening again.

I’ll do some more digging to see if I can find more on this. The above improvement will be shipped with one of the coming updates.

I’ll keep you posted if I find anything else.

@3cstudio sorry to hear you ran into issues with Burst! Thanks for reporting the issue here.

The only thing that is recurring on the dashboard, is the “live” visitors view. It refreshes only every 5 seconds or so, so doesn’t explain the flood of requests. It sounds like an infinite loop was created somehow, but don’t know at the moment how that could happen.

I’ll see if I can reproduce it, by leaving open the dashboard for a long time, and see if something similar happens.

@maggysantos7 This is probably an incompatibility with previous versions of WordPress. You can either upgrade WordPress to the latest version, or install latest version of Burst from GitHub: https://github.com/burst-Statistics/burst

This version will be released in a few weeks. It includes a backward compatibility fix with older WordPress versions.

@shayshay18 Can you try the below version?

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, so as alternative you can also wait until the next update, expected in one or two weeks.

Hi @apollosk,

Can you share domain so we can take a look at your site? I haven’t seen this before, so not sure what could cause it. Maybe there’s something non-standard in the domain or something like that?

Hi @mplanet5,

He traducido lo siguiente con la ayuda del traductor de Google. Espero que sea correcto. Realmente necesito algo de información para poder encontrar la causa del problema que estás experimentando.

?Puedes enumerar la siguiente información?

– Versión de WordPress
– Versión de PHP
– Lista de complementos
– Tema
– ?Hay alguna personalización en el código?
– ?También tienes el problema con la depuración deshabilitada? Veo muchos errores en tu sitio, que también podrían romper las cosas.